com.aliyun.sdk.service.sts20150401

类 DefaultAsyncClient

java.lang.Object

com.aliyun.sdk.service.sts20150401.DefaultAsyncClient

所有已实现的接口:

com.aliyun.core.utils.SdkAutoCloseable, AsyncClient, AutoCloseable

public final class DefaultAsyncClient
extends Object
implements AsyncClient

Main client.

字段概要

字段

限定符和类型	字段和说明
protected Map<String,String>	endpointMap
protected String	endpointRule
protected darabonba.core.TeaAsyncHandler	handler
protected String	product
protected darabonba.core.TeaRequest	REQUEST
protected String	version

构造器概要

构造器

限定符	构造器和说明
protected	DefaultAsyncClient(darabonba.core.client.ClientConfiguration configuration)

方法概要

限定符和类型	方法和说明
CompletableFuture<AssumeRoleResponse>	assumeRole(AssumeRoleRequest request) ### Prerequisites You cannot use an Alibaba Cloud account to call this operation.
CompletableFuture<AssumeRoleWithOIDCResponse>	assumeRoleWithOIDC(AssumeRoleWithOIDCRequest request) ### Prerequisites * An OIDC token is obtained from an external identity provider (IdP)
CompletableFuture<AssumeRoleWithSAMLResponse>	assumeRoleWithSAML(AssumeRoleWithSAMLRequest request) ### * A SAML response is obtained from an external identity provider (IdP)
void	close()
CompletableFuture<GetCallerIdentityResponse>	getCallerIdentity(GetCallerIdentityRequest request)

从类继承的方法 java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

从接口继承的方法 com.aliyun.sdk.service.sts20150401.AsyncClient

builder, create

字段详细资料

product

protected final String product

version

protected final String version

endpointRule

protected final String endpointRule

endpointMap

protected final Map<String,String> endpointMap

REQUEST

protected final darabonba.core.TeaRequest REQUEST

handler

protected final darabonba.core.TeaAsyncHandler handler

构造器详细资料

DefaultAsyncClient

protected DefaultAsyncClient(darabonba.core.client.ClientConfiguration configuration)

方法详细资料

close

public void close()

指定者:

close 在接口中 com.aliyun.core.utils.SdkAutoCloseable

指定者:

close 在接口中 AutoCloseable

assumeRole

public CompletableFuture<AssumeRoleResponse> assumeRole(AssumeRoleRequest request)

### Prerequisites You cannot use an Alibaba Cloud account to call this operation. The requester of this operation can only be a RAM user or RAM role. Make sure that the AliyunSTSAssumeRoleAccess policy is attached to the requester. After this policy is attached to the requester, the requester has the management permissions on STS. If you do not attach the AliyunSTSAssumeRoleAccess policy to the requester, the following error message is returned: `You are not authorized to do this action. You should be authorized by RAM.` You can refer to the following information to troubleshoot the error: * Cause of the error: The policy that is required to assume a RAM role is not attached to the requester. To resolve this issue, attach the AliyunSTSAssumeRoleAccess policy or a custom policy to the requester. For more information, see [Can I specify the RAM role that a RAM user can assume?](~~39744~~) and [Grant permissions to a RAM user](~~116146~~). * Cause of the error: The requester is not authorized to assume the RAM role. To resolve this issue, add the requester to the Principal element in the trust policy of the RAM role For more information, see [Edit the trust policy of a RAM role](~~116819~~). ### Best practices An STS token is valid for a period of time after it is issued, and the number of STS tokens that can be issued within an interval is also limited. Therefore, we recommend that you configure a proper validity period for an STS token and repeatedly use the token within this period. This prevents frequent issuing of STS tokens from adversely affecting your services if a large number of requests are sent. For more information about the limit, see [Is the number of STS API requests limited?](~~39744~~) You can configure the `DurationSeconds` parameter to specify a validity period for an STS token. When you upload or download Object Storage Service (OSS) objects on mobile devices, a large number of STS API requests are sent. In this case, repeated use of an STS token may not meet your business requirements. To avoid the limit on STS API requests from affecting access to OSS, you can **add a signature to the URL of an OSS object**. For more information, see [Add signatures to URLs](~~31952~~) and [Obtain signature information from the server and upload data to OSS](~~31926~~).

指定者:

assumeRole 在接口中 AsyncClient

assumeRoleWithOIDC

public CompletableFuture<AssumeRoleWithOIDCResponse> assumeRoleWithOIDC(AssumeRoleWithOIDCRequest request)

### Prerequisites * An OIDC token is obtained from an external identity provider (IdP). * An OIDC IdP is created in the RAM console. For more information, see [Create an OIDC IdP](~~327123~~) or [CreateOIDCProvider](~~327135~~). * A RAM role whose trusted entity is an OIDC IdP is created in the RAM console. For more information, see [Create a RAM role for a trusted IdP](~~116805~~) or [CreateRole](~~28710~~).

指定者:

assumeRoleWithOIDC 在接口中 AsyncClient

assumeRoleWithSAML

public CompletableFuture<AssumeRoleWithSAMLResponse> assumeRoleWithSAML(AssumeRoleWithSAMLRequest request)

### * A SAML response is obtained from an external identity provider (IdP). * A SAML IdP is created in the RAM console. For more information, see [Create a SAML IdP](~~116083~~) or [CreateSAMLProvider](~~186846~~). * A RAM role whose trusted entity is a SAML IdP is created in the RAM console. For more information, see [Create a RAM role for a trusted IdP](~~116805~~) or [CreateRole](~~28710~~).

指定者:

assumeRoleWithSAML 在接口中 AsyncClient

getCallerIdentity

public CompletableFuture<GetCallerIdentityResponse> getCallerIdentity(GetCallerIdentityRequest request)

指定者:

getCallerIdentity 在接口中 AsyncClient