Sts/2015-04-01) OpenAPI adopts RPC Signature style. See signature details in Description of the signature mechanism. We have packaged SDKs for common programming languages for developers. Developers can directly call the OpenAPI of this product by downloading the SDK without paying attention to the technical details. If the existing SDK cannot meet the usage requirements, you can connect through the signature mechanism. It will take about 5 working days. Therefore, it is recommended to join our DingTalk service group (11370001915) and sign under the guidance of experts.
Before using the API, you need to prepare your identity account and access key (AccessKey) to effectively access the API through client tools (SDK, CLI, etc.). For details see getAccessKey.
|AssumeRole||AssumeRole||Obtains a Security Token Service (STS) token to assume a Resource Access Management (RAM) role.|
|AssumeRoleWithSAML||AssumeRoleWithSAML||Obtains a Security Token Service (STS) token to assume a Resource Access Management (RAM) role during role-based single sign-on (SSO) by using Security Assertion Markup Language (SAML).|
|AssumeRoleWithOIDC||AssumeRoleWithOIDC||Queries a Security Token Service (STS) token to assume a Resource Access Management (RAM) role during role-based single sign-on (SSO) by using OpenID Connect (OIDC).|
|GetCallerIdentity||GetCallerIdentity||Queries the identity of the current requester.|