All Downloads are FREE. Search and download functionalities are using the official Maven repository.

com.amazonaws.services.securitytoken.AWSSecurityTokenServiceClient Maven / Gradle / Ivy

Go to download

The AWS SDK for Java Mobile - Core module holds the classes that is used by the individual service clients to interact with Amazon Web Services. Users need to depend on aws-java-sdk artifact for accessing individual client classes.

There is a newer version: 2.6.19
Show newest version
/*
 * Copyright 2010-2018 Amazon.com, Inc. or its affiliates. All Rights Reserved.
 *
 * Licensed under the Apache License, Version 2.0 (the "License").
 * You may not use this file except in compliance with the License.
 * A copy of the License is located at
 *
 *  http://aws.amazon.com/apache2.0
 *
 * or in the "license" file accompanying this file. This file is distributed
 * on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either
 * express or implied. See the License for the specific language governing
 * permissions and limitations under the License.
 */

package com.amazonaws.services.securitytoken;

import org.w3c.dom.*;

import java.util.*;

import com.amazonaws.*;
import com.amazonaws.auth.*;
import com.amazonaws.handlers.*;
import com.amazonaws.http.*;
import com.amazonaws.internal.*;
import com.amazonaws.metrics.*;
import com.amazonaws.transform.*;
import com.amazonaws.util.*;
import com.amazonaws.util.AWSRequestMetrics.Field;

import com.amazonaws.services.securitytoken.model.*;
import com.amazonaws.services.securitytoken.model.transform.*;

/**
 * Client for accessing AWS Security Token Service. All service calls made using
 * this client are blocking, and will not return until the service call
 * completes.
 * 

* AWS Security Token Service *

* The AWS Security Token Service (STS) is a web service that enables you to * request temporary, limited-privilege credentials for AWS Identity and Access * Management (IAM) users or for users that you authenticate (federated users). * This guide provides descriptions of the STS API. For more detailed * information about using this service, go to Temporary Security Credentials. *

* *

* As an alternative to using the API, you can use one of the AWS SDKs, which * consist of libraries and sample code for various programming languages and * platforms (Java, Ruby, .NET, iOS, Android, etc.). The SDKs provide a * convenient way to create programmatic access to STS. For example, the SDKs * take care of cryptographically signing requests, managing errors, and * retrying requests automatically. For information about the AWS SDKs, * including how to download and install them, see the Tools for Amazon Web Services page. *

*
*

* For information about setting up signatures and authorization through the * API, go to Signing AWS API Requests in the AWS General Reference. For * general information about the Query API, go to Making Query Requests in Using IAM. For information about using * security tokens with other AWS products, go to AWS Services That Work with IAM in the IAM User Guide. *

*

* If you're new to AWS and need additional technical information about a * specific AWS product, you can find the product's technical documentation at * http://aws.amazon.com/ * documentation/. *

*

* Endpoints *

*

* The AWS Security Token Service (STS) has a default endpoint of * https://sts.amazonaws.com that maps to the US East (N. Virginia) region. * Additional regions are available and are activated by default. For more * information, see Activating and Deactivating AWS STS in an AWS Region in the IAM User * Guide. *

*

* For information about STS endpoints, see Regions and Endpoints in the AWS General Reference. *

*

* Recording API requests *

*

* STS supports AWS CloudTrail, which is a service that records AWS calls for * your AWS account and delivers log files to an Amazon S3 bucket. By using * information collected by CloudTrail, you can determine what requests were * successfully made to STS, who made the request, when it was made, and so on. * To learn more about CloudTrail, including how to turn it on and find your log * files, see the AWS CloudTrail User Guide. *

*/ public class AWSSecurityTokenServiceClient extends AmazonWebServiceClient implements AWSSecurityTokenService { /** Provider for AWS credentials. */ private AWSCredentialsProvider awsCredentialsProvider; /** * List of exception unmarshallers for all AWS Security Token Service * exceptions. */ protected final List> exceptionUnmarshallers = new ArrayList>(); /** * Constructs a new client to invoke service methods on * AWSSecurityTokenService. A credentials provider chain will be used that * searches for credentials in this order: *
    *
  • Environment Variables - AWS_ACCESS_KEY_ID and AWS_SECRET_KEY
  • *
  • Java System Properties - aws.accessKeyId and aws.secretKey
  • *
  • Instance profile credentials delivered through the Amazon EC2 * metadata service
  • *
*

* All service calls made using this new client object are blocking, and * will not return until the service call completes. * * @see DefaultAWSCredentialsProviderChain */ @Deprecated public AWSSecurityTokenServiceClient() { this(new DefaultAWSCredentialsProviderChain(), new ClientConfiguration()); } /** * Constructs a new client to invoke service methods on * AWSSecurityTokenService. A credentials provider chain will be used that * searches for credentials in this order: *

    *
  • Environment Variables - AWS_ACCESS_KEY_ID and AWS_SECRET_KEY
  • *
  • Java System Properties - aws.accessKeyId and aws.secretKey
  • *
  • Instance profile credentials delivered through the Amazon EC2 * metadata service
  • *
*

* All service calls made using this new client object are blocking, and * will not return until the service call completes. * * @param clientConfiguration The client configuration options controlling * how this client connects to AWSSecurityTokenService (ex: proxy * settings, retry counts, etc.). * @see DefaultAWSCredentialsProviderChain */ @Deprecated public AWSSecurityTokenServiceClient(ClientConfiguration clientConfiguration) { this(new DefaultAWSCredentialsProviderChain(), clientConfiguration); } /** * Constructs a new client to invoke service methods on * AWSSecurityTokenService using the specified AWS account credentials. *

* If AWS session credentials are passed in, then those credentials will be * used to authenticate requests. Otherwise, if AWS long-term credentials * are passed in, then session management will be handled automatically by * the SDK. Callers are encouraged to use long-term credentials and let the * SDK handle starting and renewing sessions. *

* Automatically managed sessions will be shared among all clients that use * the same credentials and service endpoint. To opt out of this behavior, * explicitly provide an instance of {@link AWSCredentialsProvider} that * returns {@link AWSSessionCredentials}. *

* All service calls made using this new client object are blocking, and * will not return until the service call completes. * * @param awsCredentials The AWS credentials (access key ID and secret key) * to use when authenticating with AWS services. */ public AWSSecurityTokenServiceClient(AWSCredentials awsCredentials) { this(awsCredentials, new ClientConfiguration()); } /** * Constructs a new client to invoke service methods on * AWSSecurityTokenService using the specified AWS account credentials and * client configuration options. *

* If AWS session credentials are passed in, then those credentials will be * used to authenticate requests. Otherwise, if AWS long-term credentials * are passed in, then session management will be handled automatically by * the SDK. Callers are encouraged to use long-term credentials and let the * SDK handle starting and renewing sessions. *

* Automatically managed sessions will be shared among all clients that use * the same credentials and service endpoint. To opt out of this behavior, * explicitly provide an instance of {@link AWSCredentialsProvider} that * returns {@link AWSSessionCredentials}. *

* All service calls made using this new client object are blocking, and * will not return until the service call completes. * * @param awsCredentials The AWS credentials (access key ID and secret key) * to use when authenticating with AWS services. * @param clientConfiguration The client configuration options controlling * how this client connects to AWSSecurityTokenService (ex: proxy * settings, retry counts, etc.). */ public AWSSecurityTokenServiceClient(AWSCredentials awsCredentials, ClientConfiguration clientConfiguration) { this(new StaticCredentialsProvider(awsCredentials), clientConfiguration); } /** * Constructs a new client to invoke service methods on * AWSSecurityTokenService using the specified AWS account credentials * provider. *

* If AWS session credentials are passed in, then those credentials will be * used to authenticate requests. Otherwise, if AWS long-term credentials * are passed in, then session management will be handled automatically by * the SDK. Callers are encouraged to use long-term credentials and let the * SDK handle starting and renewing sessions. *

* Automatically managed sessions will be shared among all clients that use * the same credentials and service endpoint. To opt out of this behavior, * explicitly provide an instance of {@link AWSCredentialsProvider} that * returns {@link AWSSessionCredentials}. *

* All service calls made using this new client object are blocking, and * will not return until the service call completes. * * @param awsCredentialsProvider The AWS credentials provider which will * provide credentials to authenticate requests with AWS * services. */ public AWSSecurityTokenServiceClient(AWSCredentialsProvider awsCredentialsProvider) { this(awsCredentialsProvider, new ClientConfiguration()); } /** * Constructs a new client to invoke service methods on * AWSSecurityTokenService using the specified AWS account credentials * provider and client configuration options. *

* If AWS session credentials are passed in, then those credentials will be * used to authenticate requests. Otherwise, if AWS long-term credentials * are passed in, then session management will be handled automatically by * the SDK. Callers are encouraged to use long-term credentials and let the * SDK handle starting and renewing sessions. *

* Automatically managed sessions will be shared among all clients that use * the same credentials and service endpoint. To opt out of this behavior, * explicitly provide an instance of {@link AWSCredentialsProvider} that * returns {@link AWSSessionCredentials}. *

* All service calls made using this new client object are blocking, and * will not return until the service call completes. * * @param awsCredentialsProvider The AWS credentials provider which will * provide credentials to authenticate requests with AWS * services. * @param clientConfiguration The client configuration options controlling * how this client connects to AWSSecurityTokenService (ex: proxy * settings, retry counts, etc.). */ public AWSSecurityTokenServiceClient(AWSCredentialsProvider awsCredentialsProvider, ClientConfiguration clientConfiguration) { this(awsCredentialsProvider, clientConfiguration, new UrlHttpClient(clientConfiguration)); } /** * Constructs a new client to invoke service methods on * AWSSecurityTokenService using the specified AWS account credentials * provider, client configuration options and request metric collector. *

* All service calls made using this new client object are blocking, and * will not return until the service call completes. * * @param awsCredentialsProvider The AWS credentials provider which will * provide credentials to authenticate requests with AWS * services. * @param clientConfiguration The client configuration options controlling * how this client connects to AWSSecurityTokenService (ex: proxy * settings, retry counts, etc.). * @param requestMetricCollector optional request metric collector */ @Deprecated public AWSSecurityTokenServiceClient(AWSCredentialsProvider awsCredentialsProvider, ClientConfiguration clientConfiguration, RequestMetricCollector requestMetricCollector) { super(adjustClientConfiguration(clientConfiguration), requestMetricCollector); this.awsCredentialsProvider = awsCredentialsProvider; init(); } /** * Constructs a new client to invoke service methods on * AWSSecurityTokenService using the specified AWS account credentials * provider, client configuration options and request metric collector. *

* All service calls made using this new client object are blocking, and * will not return until the service call completes. * * @param awsCredentialsProvider The AWS credentials provider which will * provide credentials to authenticate requests with AWS * services. * @param clientConfiguration The client configuration options controlling * how this client connects to AWSSecurityTokenService (ex: proxy * settings, retry counts, etc.). * @param httpClient A http client */ public AWSSecurityTokenServiceClient(AWSCredentialsProvider awsCredentialsProvider, ClientConfiguration clientConfiguration, HttpClient httpClient) { super(adjustClientConfiguration(clientConfiguration), httpClient); this.awsCredentialsProvider = awsCredentialsProvider; init(); } private void init() { exceptionUnmarshallers.add(new ExpiredTokenExceptionUnmarshaller()); exceptionUnmarshallers.add(new IDPCommunicationErrorExceptionUnmarshaller()); exceptionUnmarshallers.add(new IDPRejectedClaimExceptionUnmarshaller()); exceptionUnmarshallers.add(new InvalidIdentityTokenExceptionUnmarshaller()); exceptionUnmarshallers.add(new MalformedPolicyDocumentExceptionUnmarshaller()); exceptionUnmarshallers.add(new PackedPolicyTooLargeExceptionUnmarshaller()); exceptionUnmarshallers.add(new RegionDisabledExceptionUnmarshaller()); exceptionUnmarshallers.add(new StandardErrorUnmarshaller()); // calling this.setEndPoint(...) will also modify the signer accordingly this.setEndpoint("sts.amazonaws.com"); this.endpointPrefix = "sts"; HandlerChainFactory chainFactory = new HandlerChainFactory(); requestHandler2s.addAll(chainFactory.newRequestHandlerChain( "/com/amazonaws/services/securitytoken/request.handlers")); requestHandler2s.addAll(chainFactory.newRequestHandler2Chain( "/com/amazonaws/services/securitytoken/request.handler2s")); } private static ClientConfiguration adjustClientConfiguration(ClientConfiguration orig) { ClientConfiguration config = orig; return config; } /** *

* Returns a set of temporary security credentials (consisting of an access * key ID, a secret access key, and a security token) that you can use to * access AWS resources that you might not normally have access to. * Typically, you use AssumeRole for cross-account access or * federation. For a comparison of AssumeRole with the other * APIs that produce temporary credentials, see Requesting Temporary Security Credentials and Comparing the AWS STS APIs in the IAM User Guide. *

*

* Important: You cannot call AssumeRole by using AWS * root account credentials; access is denied. You must use credentials for * an IAM user or an IAM role to call AssumeRole. *

*

* For cross-account access, imagine that you own multiple accounts and need * to access resources in each account. You could create long-term * credentials in each account to access those resources. However, managing * all those credentials and remembering which one can access which account * can be time consuming. Instead, you can create one set of long-term * credentials in one account and then use temporary security credentials to * access all the other accounts by assuming roles in those accounts. For * more information about roles, see IAM * Roles (Delegation and Federation) in the IAM User Guide. *

*

* For federation, you can, for example, grant single sign-on access to the * AWS Management Console. If you already have an identity and * authentication system in your corporate network, you don't have to * recreate user identities in AWS in order to grant those user identities * access to AWS. Instead, after a user has been authenticated, you call * AssumeRole (and specify the role with the appropriate * permissions) to get temporary security credentials for that user. With * those temporary security credentials, you construct a sign-in URL that * users can use to access the console. For more information, see Common Scenarios for Temporary Credentials in the IAM User * Guide. *

*

* The temporary security credentials are valid for the duration that you * specified when calling AssumeRole, which can be from 900 * seconds (15 minutes) to a maximum of 3600 seconds (1 hour). The default * is 1 hour. *

*

* The temporary security credentials created by AssumeRole can * be used to make API calls to any AWS service with the following * exception: you cannot call the STS service's * GetFederationToken or GetSessionToken APIs. *

*

* Optionally, you can pass an IAM access policy to this operation. If you * choose not to pass a policy, the temporary security credentials that are * returned by the operation have the permissions that are defined in the * access policy of the role that is being assumed. If you pass a policy to * this operation, the temporary security credentials that are returned by * the operation have the permissions that are allowed by both the access * policy of the role that is being assumed, and the policy * that you pass. This gives you a way to further restrict the permissions * for the resulting temporary security credentials. You cannot use the * passed policy to grant permissions that are in excess of those allowed by * the access policy of the role that is being assumed. For more * information, see Permissions for AssumeRole, AssumeRoleWithSAML, and * AssumeRoleWithWebIdentity in the IAM User Guide. *

*

* To assume a role, your AWS account must be trusted by the role. The trust * relationship is defined in the role's trust policy when the role is * created. That trust policy states which accounts are allowed to delegate * access to this account's role. *

*

* The user who wants to access the role must also have permissions * delegated from the role's administrator. If the user is in a different * account than the role, then the user's administrator must attach a policy * that allows the user to call AssumeRole on the ARN of the role in the * other account. If the user is in the same account as the role, then you * can either attach a policy to the user (identical to the previous * different account user), or you can add the user as a principal directly * in the role's trust policy *

*

* Using MFA with AssumeRole *

*

* You can optionally include multi-factor authentication (MFA) information * when you call AssumeRole. This is useful for cross-account * scenarios in which you want to make sure that the user who is assuming * the role has been authenticated using an AWS MFA device. In that * scenario, the trust policy of the role being assumed includes a condition * that tests for MFA authentication; if the caller does not include valid * MFA information, the request to assume the role is denied. The condition * in a trust policy that tests for MFA authentication might look like the * following example. *

*

* "Condition": {"Bool": {"aws:MultiFactorAuthPresent": true}} *

*

* For more information, see Configuring MFA-Protected API Access in the IAM User Guide * guide. *

*

* To use MFA with AssumeRole, you pass values for the * SerialNumber and TokenCode parameters. The * SerialNumber value identifies the user's hardware or virtual * MFA device. The TokenCode is the time-based one-time * password (TOTP) that the MFA devices produces. *

* * @param assumeRoleRequest * @return assumeRoleResult The response from the AssumeRole service method, * as returned by AWS Security Token Service. * @throws MalformedPolicyDocumentException * @throws PackedPolicyTooLargeException * @throws RegionDisabledException * @throws AmazonClientException If any internal errors are encountered * inside the client while attempting to make the request or * handle the response. For example if a network connection is * not available. * @throws AmazonServiceException If an error response is returned by AWS * Security Token Service indicating either a problem with the * data in the request, or a server side issue. */ public AssumeRoleResult assumeRole(AssumeRoleRequest assumeRoleRequest) throws AmazonServiceException, AmazonClientException { ExecutionContext executionContext = createExecutionContext(assumeRoleRequest); AWSRequestMetrics awsRequestMetrics = executionContext.getAwsRequestMetrics(); awsRequestMetrics.startEvent(Field.ClientExecuteTime); Request request = null; Response response = null; try { request = new AssumeRoleRequestMarshaller().marshall(assumeRoleRequest); // Binds the request metrics to the current request. request.setAWSRequestMetrics(awsRequestMetrics); response = invoke(request, new AssumeRoleResultStaxUnmarshaller(), executionContext); return response.getAwsResponse(); } finally { endClientExecution(awsRequestMetrics, request, response); } } /** *

* Returns a set of temporary security credentials for users who have been * authenticated in a mobile or web application with a web identity * provider, such as Amazon Cognito, Login with Amazon, Facebook, Google, or * any OpenID Connect-compatible identity provider. *

* *

* For mobile applications, we recommend that you use Amazon Cognito. You * can use Amazon Cognito with the AWS SDK for iOS and the AWS SDK for Android to * uniquely identify a user and supply the user with a consistent identity * throughout the lifetime of an application. *

*

* To learn more about Amazon Cognito, see Amazon Cognito Overview in the AWS SDK for Android Developer * Guide guide and Amazon Cognito Overview in the AWS SDK for iOS Developer * Guide. *

*
*

* Calling AssumeRoleWithWebIdentity does not require the use * of AWS security credentials. Therefore, you can distribute an application * (for example, on mobile devices) that requests temporary security * credentials without including long-term AWS credentials in the * application, and without deploying server-based proxy services that use * long-term AWS credentials. Instead, the identity of the caller is * validated by using a token from the web identity provider. For a * comparison of AssumeRoleWithWebIdentity with the other APIs * that produce temporary credentials, see Requesting Temporary Security Credentials and Comparing the AWS STS APIs in the IAM User Guide. *

*

* The temporary security credentials returned by this API consist of an * access key ID, a secret access key, and a security token. Applications * can use these temporary security credentials to sign calls to AWS service * APIs. *

*

* The credentials are valid for the duration that you specified when * calling AssumeRoleWithWebIdentity, which can be from 900 * seconds (15 minutes) to a maximum of 3600 seconds (1 hour). The default * is 1 hour. *

*

* The temporary security credentials created by * AssumeRoleWithWebIdentity can be used to make API calls to * any AWS service with the following exception: you cannot call the STS * service's GetFederationToken or GetSessionToken * APIs. *

*

* Optionally, you can pass an IAM access policy to this operation. If you * choose not to pass a policy, the temporary security credentials that are * returned by the operation have the permissions that are defined in the * access policy of the role that is being assumed. If you pass a policy to * this operation, the temporary security credentials that are returned by * the operation have the permissions that are allowed by both the access * policy of the role that is being assumed, and the policy * that you pass. This gives you a way to further restrict the permissions * for the resulting temporary security credentials. You cannot use the * passed policy to grant permissions that are in excess of those allowed by * the access policy of the role that is being assumed. For more * information, see Permissions for AssumeRole, AssumeRoleWithSAML, and * AssumeRoleWithWebIdentity in the IAM User Guide. *

*

* Before your application can call AssumeRoleWithWebIdentity, * you must have an identity token from a supported identity provider and * create a role that the application can assume. The role that your * application assumes must trust the identity provider that is associated * with the identity token. In other words, the identity provider must be * specified in the role's trust policy. *

* *

* Calling AssumeRoleWithWebIdentity can result in an entry in * your AWS CloudTrail logs. The entry includes the Subject of the provided Web Identity Token. We recommend that you * avoid using any personally identifiable information (PII) in this field. * For example, you could instead use a GUID or a pairwise identifier, as suggested in the OIDC specification. *

*
*

* For more information about how to use web identity federation and the * AssumeRoleWithWebIdentity API, see the following resources: *

* * * @param assumeRoleWithWebIdentityRequest * @return assumeRoleWithWebIdentityResult The response from the * AssumeRoleWithWebIdentity service method, as returned by AWS * Security Token Service. * @throws MalformedPolicyDocumentException * @throws PackedPolicyTooLargeException * @throws IDPRejectedClaimException * @throws IDPCommunicationErrorException * @throws InvalidIdentityTokenException * @throws ExpiredTokenException * @throws RegionDisabledException * @throws AmazonClientException If any internal errors are encountered * inside the client while attempting to make the request or * handle the response. For example if a network connection is * not available. * @throws AmazonServiceException If an error response is returned by AWS * Security Token Service indicating either a problem with the * data in the request, or a server side issue. */ public AssumeRoleWithWebIdentityResult assumeRoleWithWebIdentity( AssumeRoleWithWebIdentityRequest assumeRoleWithWebIdentityRequest) throws AmazonServiceException, AmazonClientException { ExecutionContext executionContext = createExecutionContext(assumeRoleWithWebIdentityRequest); AWSRequestMetrics awsRequestMetrics = executionContext.getAwsRequestMetrics(); awsRequestMetrics.startEvent(Field.ClientExecuteTime); Request request = null; Response response = null; try { request = new AssumeRoleWithWebIdentityRequestMarshaller() .marshall(assumeRoleWithWebIdentityRequest); // Binds the request metrics to the current request. request.setAWSRequestMetrics(awsRequestMetrics); response = invoke(request, new AssumeRoleWithWebIdentityResultStaxUnmarshaller(), executionContext); return response.getAwsResponse(); } finally { endClientExecution(awsRequestMetrics, request, response); } } /** *

* Returns details about the IAM identity whose credentials are used to call * the API. *

* * @param getCallerIdentityRequest * @return getCallerIdentityResult The response from the GetCallerIdentity * service method, as returned by AWS Security Token Service. * @throws AmazonClientException If any internal errors are encountered * inside the client while attempting to make the request or * handle the response. For example if a network connection is * not available. * @throws AmazonServiceException If an error response is returned by AWS * Security Token Service indicating either a problem with the * data in the request, or a server side issue. */ public GetCallerIdentityResult getCallerIdentity( GetCallerIdentityRequest getCallerIdentityRequest) throws AmazonServiceException, AmazonClientException { ExecutionContext executionContext = createExecutionContext(getCallerIdentityRequest); AWSRequestMetrics awsRequestMetrics = executionContext.getAwsRequestMetrics(); awsRequestMetrics.startEvent(Field.ClientExecuteTime); Request request = null; Response response = null; try { request = new GetCallerIdentityRequestMarshaller().marshall(getCallerIdentityRequest); // Binds the request metrics to the current request. request.setAWSRequestMetrics(awsRequestMetrics); response = invoke(request, new GetCallerIdentityResultStaxUnmarshaller(), executionContext); return response.getAwsResponse(); } finally { endClientExecution(awsRequestMetrics, request, response); } } /** *

* Returns a set of temporary security credentials (consisting of an access * key ID, a secret access key, and a security token) for a federated user. * A typical use is in a proxy application that gets temporary security * credentials on behalf of distributed applications inside a corporate * network. Because you must call the GetFederationToken action * using the long-term security credentials of an IAM user, this call is * appropriate in contexts where those credentials can be safely stored, * usually in a server-based application. For a comparison of * GetFederationToken with the other APIs that produce * temporary credentials, see Requesting Temporary Security Credentials and Comparing the AWS STS APIs in the IAM User Guide. *

* *

* If you are creating a mobile-based or browser-based app that can * authenticate users using a web identity provider like Login with Amazon, * Facebook, Google, or an OpenID Connect-compatible identity provider, we * recommend that you use Amazon * Cognito or AssumeRoleWithWebIdentity. For more * information, see Federation Through a Web-based Identity Provider. *

*
*

* The GetFederationToken action must be called by using the * long-term AWS security credentials of an IAM user. You can also call * GetFederationToken using the security credentials of an AWS * root account, but we do not recommended it. Instead, we recommend that * you create an IAM user for the purpose of the proxy application and then * attach a policy to the IAM user that limits federated users to only the * actions and resources that they need access to. For more information, see * IAM * Best Practices in the IAM User Guide. *

*

* The temporary security credentials that are obtained by using the * long-term credentials of an IAM user are valid for the specified * duration, from 900 seconds (15 minutes) up to a maximium of 129600 * seconds (36 hours). The default is 43200 seconds (12 hours). Temporary * credentials that are obtained by using AWS root account credentials have * a maximum duration of 3600 seconds (1 hour). *

*

* The temporary security credentials created by * GetFederationToken can be used to make API calls to any AWS * service with the following exceptions: *

*
    *
  • *

    * You cannot use these credentials to call any IAM APIs. *

    *
  • *
  • *

    * You cannot call any STS APIs. *

    *
  • *
*

* Permissions *

*

* The permissions for the temporary security credentials returned by * GetFederationToken are determined by a combination of the * following: *

*
    *
  • *

    * The policy or policies that are attached to the IAM user whose * credentials are used to call GetFederationToken. *

    *
  • *
  • *

    * The policy that is passed as a parameter in the call. *

    *
  • *
*

* The passed policy is attached to the temporary security credentials that * result from the GetFederationToken API call--that is, to the * federated user. When the federated user makes an AWS request, AWS * evaluates the policy attached to the federated user in combination with * the policy or policies attached to the IAM user whose credentials were * used to call GetFederationToken. AWS allows the federated * user's request only when both the federated user and the * IAM user are explicitly allowed to perform the requested action. The * passed policy cannot grant more permissions than those that are defined * in the IAM user policy. *

*

* A typical use case is that the permissions of the IAM user whose * credentials are used to call GetFederationToken are designed * to allow access to all the actions and resources that any federated user * will need. Then, for individual users, you pass a policy to the operation * that scopes down the permissions to a level that's appropriate to that * individual user, using a policy that allows only a subset of permissions * that are granted to the IAM user. *

*

* If you do not pass a policy, the resulting temporary security credentials * have no effective permissions. The only exception is when the temporary * security credentials are used to access a resource that has a * resource-based policy that specifically allows the federated user to * access the resource. *

*

* For more information about how permissions work, see Permissions for GetFederationToken. For information about using * GetFederationToken to create temporary security credentials, * see GetFederationToken—Federation Through a Custom Identity Broker. *

* * @param getFederationTokenRequest * @return getFederationTokenResult The response from the GetFederationToken * service method, as returned by AWS Security Token Service. * @throws MalformedPolicyDocumentException * @throws PackedPolicyTooLargeException * @throws RegionDisabledException * @throws AmazonClientException If any internal errors are encountered * inside the client while attempting to make the request or * handle the response. For example if a network connection is * not available. * @throws AmazonServiceException If an error response is returned by AWS * Security Token Service indicating either a problem with the * data in the request, or a server side issue. */ public GetFederationTokenResult getFederationToken( GetFederationTokenRequest getFederationTokenRequest) throws AmazonServiceException, AmazonClientException { ExecutionContext executionContext = createExecutionContext(getFederationTokenRequest); AWSRequestMetrics awsRequestMetrics = executionContext.getAwsRequestMetrics(); awsRequestMetrics.startEvent(Field.ClientExecuteTime); Request request = null; Response response = null; try { request = new GetFederationTokenRequestMarshaller().marshall(getFederationTokenRequest); // Binds the request metrics to the current request. request.setAWSRequestMetrics(awsRequestMetrics); response = invoke(request, new GetFederationTokenResultStaxUnmarshaller(), executionContext); return response.getAwsResponse(); } finally { endClientExecution(awsRequestMetrics, request, response); } } /** *

* Returns a set of temporary credentials for an AWS account or IAM user. * The credentials consist of an access key ID, a secret access key, and a * security token. Typically, you use GetSessionToken if you * want to use MFA to protect programmatic calls to specific AWS APIs like * Amazon EC2 StopInstances. MFA-enabled IAM users would need * to call GetSessionToken and submit an MFA code that is * associated with their MFA device. Using the temporary security * credentials that are returned from the call, IAM users can then make * programmatic calls to APIs that require MFA authentication. If you do not * supply a correct MFA code, then the API returns an access denied error. * For a comparison of GetSessionToken with the other APIs that * produce temporary credentials, see Requesting Temporary Security Credentials and Comparing the AWS STS APIs in the IAM User Guide. *

*

* The GetSessionToken action must be called by using the * long-term AWS security credentials of the AWS account or an IAM user. * Credentials that are created by IAM users are valid for the duration that * you specify, from 900 seconds (15 minutes) up to a maximum of 129600 * seconds (36 hours), with a default of 43200 seconds (12 hours); * credentials that are created by using account credentials can range from * 900 seconds (15 minutes) up to a maximum of 3600 seconds (1 hour), with a * default of 1 hour. *

*

* The temporary security credentials created by * GetSessionToken can be used to make API calls to any AWS * service with the following exceptions: *

*
    *
  • *

    * You cannot call any IAM APIs unless MFA authentication information is * included in the request. *

    *
  • *
  • *

    * You cannot call any STS API except AssumeRole. *

    *
  • *
* *

* We recommend that you do not call GetSessionToken with root * account credentials. Instead, follow our best practices by creating one or more IAM users, giving them the * necessary permissions, and using IAM users for everyday interaction with * AWS. *

*
*

* The permissions associated with the temporary security credentials * returned by GetSessionToken are based on the permissions * associated with account or IAM user whose credentials are used to call * the action. If GetSessionToken is called using root account * credentials, the temporary credentials have root account permissions. * Similarly, if GetSessionToken is called using the * credentials of an IAM user, the temporary credentials have the same * permissions as the IAM user. *

*

* For more information about using GetSessionToken to create * temporary credentials, go to Temporary Credentials for Users in Untrusted Environments in the * IAM User Guide. *

* * @param getSessionTokenRequest * @return getSessionTokenResult The response from the GetSessionToken * service method, as returned by AWS Security Token Service. * @throws RegionDisabledException * @throws AmazonClientException If any internal errors are encountered * inside the client while attempting to make the request or * handle the response. For example if a network connection is * not available. * @throws AmazonServiceException If an error response is returned by AWS * Security Token Service indicating either a problem with the * data in the request, or a server side issue. */ public GetSessionTokenResult getSessionToken(GetSessionTokenRequest getSessionTokenRequest) throws AmazonServiceException, AmazonClientException { ExecutionContext executionContext = createExecutionContext(getSessionTokenRequest); AWSRequestMetrics awsRequestMetrics = executionContext.getAwsRequestMetrics(); awsRequestMetrics.startEvent(Field.ClientExecuteTime); Request request = null; Response response = null; try { request = new GetSessionTokenRequestMarshaller().marshall(getSessionTokenRequest); // Binds the request metrics to the current request. request.setAWSRequestMetrics(awsRequestMetrics); response = invoke(request, new GetSessionTokenResultStaxUnmarshaller(), executionContext); return response.getAwsResponse(); } finally { endClientExecution(awsRequestMetrics, request, response); } } /** *

* Returns a set of temporary credentials for an AWS account or IAM user. * The credentials consist of an access key ID, a secret access key, and a * security token. Typically, you use GetSessionToken if you * want to use MFA to protect programmatic calls to specific AWS APIs like * Amazon EC2 StopInstances. MFA-enabled IAM users would need * to call GetSessionToken and submit an MFA code that is * associated with their MFA device. Using the temporary security * credentials that are returned from the call, IAM users can then make * programmatic calls to APIs that require MFA authentication. If you do not * supply a correct MFA code, then the API returns an access denied error. * For a comparison of GetSessionToken with the other APIs that * produce temporary credentials, see Requesting Temporary Security Credentials and Comparing the AWS STS APIs in the IAM User Guide. *

*

* The GetSessionToken action must be called by using the * long-term AWS security credentials of the AWS account or an IAM user. * Credentials that are created by IAM users are valid for the duration that * you specify, from 900 seconds (15 minutes) up to a maximum of 129600 * seconds (36 hours), with a default of 43200 seconds (12 hours); * credentials that are created by using account credentials can range from * 900 seconds (15 minutes) up to a maximum of 3600 seconds (1 hour), with a * default of 1 hour. *

*

* The temporary security credentials created by * GetSessionToken can be used to make API calls to any AWS * service with the following exceptions: *

*
    *
  • *

    * You cannot call any IAM APIs unless MFA authentication information is * included in the request. *

    *
  • *
  • *

    * You cannot call any STS API except AssumeRole. *

    *
  • *
* *

* We recommend that you do not call GetSessionToken with root * account credentials. Instead, follow our best practices by creating one or more IAM users, giving them the * necessary permissions, and using IAM users for everyday interaction with * AWS. *

*
*

* The permissions associated with the temporary security credentials * returned by GetSessionToken are based on the permissions * associated with account or IAM user whose credentials are used to call * the action. If GetSessionToken is called using root account * credentials, the temporary credentials have root account permissions. * Similarly, if GetSessionToken is called using the * credentials of an IAM user, the temporary credentials have the same * permissions as the IAM user. *

*

* For more information about using GetSessionToken to create * temporary credentials, go to Temporary Credentials for Users in Untrusted Environments in the * IAM User Guide. *

* * @return getSessionTokenResult The response from the GetSessionToken * service method, as returned by AWS Security Token Service. * @throws RegionDisabledException * @throws AmazonClientException If any internal errors are encountered * inside the client while attempting to make the request or * handle the response. For example if a network connection is * not available. * @throws AmazonServiceException If an error response is returned by AWS * Security Token Service indicating either a problem with the * data in the request, or a server side issue. */ public GetSessionTokenResult getSessionToken() throws AmazonServiceException, AmazonClientException { GetSessionTokenRequest getSessionTokenRequest = new GetSessionTokenRequest(); return getSessionToken(getSessionTokenRequest); } /** *

* Returns details about the IAM identity whose credentials are used to call * the API. *

* * @return getCallerIdentityResult The response from the GetCallerIdentity * service method, as returned by AWS Security Token Service. * @throws AmazonClientException If any internal errors are encountered * inside the client while attempting to make the request or * handle the response. For example if a network connection is * not available. * @throws AmazonServiceException If an error response is returned by AWS * Security Token Service indicating either a problem with the * data in the request, or a server side issue. */ public GetCallerIdentityResult getCallerIdentity() throws AmazonServiceException, AmazonClientException { GetCallerIdentityRequest getCallerIdentityRequest = new GetCallerIdentityRequest(); return getCallerIdentity(getCallerIdentityRequest); } /** * Returns additional metadata for a previously executed successful, * request, typically used for debugging issues where a service isn't acting * as expected. This data isn't considered part of the result data returned * by an operation, so it's available through this separate, diagnostic * interface. *

* Response metadata is only cached for a limited period of time, so if you * need to access this extra diagnostic information for an executed request, * you should use this method to retrieve it as soon as possible after * executing the request. * * @param request The originally executed request * @return The response metadata for the specified request, or null if none * is available. * @deprecated ResponseMetadata cache can hold up to 50 requests and * responses in memory and will cause memory issue. This method * now always returns null. */ @Deprecated public ResponseMetadata getCachedResponseMetadata(AmazonWebServiceRequest request) { return client.getResponseMetadataForRequest(request); } private Response invoke(Request request, Unmarshaller unmarshaller, ExecutionContext executionContext) { request.setEndpoint(endpoint); request.setTimeOffset(timeOffset); AmazonWebServiceRequest originalRequest = request.getOriginalRequest(); AWSCredentials credentials = awsCredentialsProvider.getCredentials(); if (originalRequest.getRequestCredentials() != null) { credentials = originalRequest.getRequestCredentials(); } executionContext.setCredentials(credentials); StaxResponseHandler responseHandler = new StaxResponseHandler(unmarshaller); DefaultErrorResponseHandler errorResponseHandler = new DefaultErrorResponseHandler( exceptionUnmarshallers); return client.execute(request, responseHandler, errorResponseHandler, executionContext); } }





© 2015 - 2024 Weber Informatics LLC | Privacy Policy