This is the multi-page printable view of this section. .
Security Token Service (STS)
The MinIO Security Token Service (STS) APIs allow applications to generate temporary credentials for accessing the MinIO deployment.
The STS API is required for MinIO deployments configured to use external identity managers, as the API allows conversion of the external IDP credentials into AWS Signature v4-compatible credentials.
STS API Endpoints
MinIO supports the following STS API endpoints:
| Endpoint | Supported IDP | Description |
|---|---|---|
| AssumeRoleWithWebIdentity | OpenID Connect | Generates an access key and secret key using the JWT token returned by the OIDC provider |
| AssumeRoleWithLDAPIdentity | Active Directory / LDAP | Generates an access key and secret key using the AD/LDAP credentials specified to the API endpoint. |
| AssumeRoleWithCustomToken | MinIO Identity Plugin | Exchanges a token from an external identity provider for temporary S3 credentials using the MinIO Identity Plugin. |
All three APIs return an access key, secret key, and session token. Pass all three to the S3 SDK. Session lifetimes follow each endpoint’s contract; LDAP, OIDC, and the identity plugin do not share one universal duration limit.
1 - AssumeRoleWithCustomToken
The MinIO Security Token Service (STS) AssumeRoleWithCustomToken API endpoint exchanges a token validated by the MinIO External Identity Management Plugin for temporary S3 credentials.
Request Endpoint
The AssumeRoleWithCustomToken endpoint has the following form:
The following example uses all supported arguments. Replace the minio.example.net hostname with the appropriate URL for your MinIO cluster:
Request Query Parameters
This endpoint supports the following query parameters:
Parameter |
Type |
Description |
|---|---|---|
|
string |
Required Specify the JSON Token to present to the external identity manager. MinIO expects the identity manager to parse the token and determine whether to authenticate client requests using that token. |
|
string |
Required Specify |
|
string |
Required Specify the ARN for the Identity Manager Plugin configuration to associate with this STS request. See Note that MinIO automatically prepends |
|
integer |
Optional Specify the number of seconds after which the temporary credentials expire.
If omitted, SILO uses the identity plugin's |
Response Elements
MinIO returns an AssumeRoleWithCustomTokenResult object, where the Credentials object contains the temporary credentials generated by MinIO:
AccessKeyId- The access key applications use for authentication.SecretAccessKey- The secret key applications use for authentication.Expiration- The RFC3339 date and time after which the credentials expire.SessionToken- Required with the access key and secret key when signing S3 requests with these temporary credentials.
The following example is similar to the response returned by the MinIO STS AssumeRoleWithCustomToken endpoint:
Error Elements
The XML error response for this API endpoint is similar to the AWS AssumeRoleWithWebIdentity response.
2 - AssumeRoleWithLDAPIdentity
The MinIO Security Token Service (STS) AssumeRoleWithLDAPIdentity API endpoint generates temporary access credentials using Active Directory or LDAP user credentials. This page documents the MinIO server AssumeRoleWithLDAPIdentity endpoint. For instructions on implementing STS using an S3-compatible SDK, defer to the documentation for that SDK.
The MinIO STS AssumeRoleWithLDAPIdentity API endpoint is modeled after the AWS AssumeRoleWithWebIdentity endpoint and shares certain request/response elements. This page documents the MinIO-specific syntax and links out to the AWS reference for all shared elements.
Request Endpoint
The AssumeRoleWithLDAPIdentity endpoint has the following form:
The following example shows the required arguments and an optional session duration. Replace the minio.example.net hostname with the appropriate URL for your MinIO cluster:
Request Query Parameters
This endpoint supports the following query parameters:
Parameter |
Type |
Description |
|---|---|---|
|
string |
Required Specify the username of the AD/LDAP user as whom you want to authenticate. |
|
string |
Required Specify the password for the |
|
string |
Required Specify |
|
integer |
Optional Specify the number of seconds after which the temporary credentials
expire. Defaults to
This endpoint authenticates LDAP credentials, not a JWT. It does not obtain the session duration from an incoming JWT |
|
string |
Optional Specify the URL-encoded JSON-formatted policy to use as an inline session policy.
The resulting permissions for the temporary credentials are the
intersection between the policy matching the Distinguished
Name (DN) of the The inline policy can specify a subset of permissions allowed by the policy specified in the DN policy. Applications can never assume more privileges than those specified in the DN policy. Omit to use only the DN policy. See Access Management for more information on MinIO authentication and authorization. |
Response Elements
AssumeRoleWithLDAPIdentity is a SILO/MinIO extension, not an AWS STS action. SILO returns an AssumeRoleWithLDAPIdentityResult containing a Credentials element with:
AccessKeyId- The access key applications use for authentication.SecretAccessKey- The secret key applications use for authentication.Expiration- The RFC3339 date and time after which the credentials expire.SessionToken- Required with the access key and secret key when signing S3 requests with these temporary credentials.
The following example is similar to the response returned by the MinIO STS AssumeRoleWithLDAPIdentity endpoint:
Error Elements
The XML error response for this API endpoint is similar to the AWS STS error response.
3 - AssumeRoleWithWebIdentity
The MinIO Security Token Service (STS) AssumeRoleWithWebIdentity API endpoint generates temporary access credentials using a JSON Web Token (JWT) returned from a configured OpenID IDentity Provider (IDP). This page documents the MinIO server AssumeRoleWithWebIdentity endpoint. For instructions on implementing STS using an S3-compatible SDK, defer to the documentation for that SDK.
The MinIO STS AssumeRoleWithWebIdentity API endpoint is modeled after the AWS AssumeRoleWithWebIdentity endpoint and shares certain request/response elements. This page documents the MinIO-specific syntax and links out to the AWS reference for all shared elements.
Request Endpoint
The AssumeRoleWithWebIdentity endpoint has the following form:
The following example uses all supported arguments. Replace the minio.example.net hostname with the appropriate URL for your MinIO cluster:
Request Query Parameters
This endpoint supports the following query parameters:
Parameter |
Type |
Description |
|---|---|---|
|
string |
Required Specify the JSON Web Token (JWT) returned by the configured OpenID IDentity Provider. |
|
string |
Required Specify |
|
integer |
Optional Specify the number of seconds after which the temporary credentials
expire. Without a server override, an explicit duration must be between If omitted, SILO retains the validated JWT's |
|
string |
Optional Specify the URL-encoded JSON-formatted policy to use as an inline session policy.
The resulting permissions for the temporary credentials are the intersection between the policy specified as part of the JWT claim and the specified inline policy. Applications can only perform those operations for which they are explicitly authorized. The inline policy can specify a subset of permissions allowed by the policy specified in the JWT claim. Applications can never assume more privileges than those specified in the JWT claim policy. Omit to use only the JWT claim policy. See Access Management for more information on MinIO authentication and authorization. |
|
string |
Optional The role Amazon Resource Number (ARN) to use for all user authentication requests.
If used, there must be a matching OIDC RolePolicy defined for the RoleArn’s provider by the When used, all valid authorization requests assume the same set of permissions provided by the RolePolicy. You can use OpenID Policy Variables to create policies that programmatically manage what each individual user has access to. If you do not supply a RoleArn, MinIO attempts to authorize through a JWT-based claim. |
Response Elements
The XML response for this API endpoint is similar to the AWS AssumeRoleWithWebIdentity response. Specifically, MinIO returns an AssumeRoleWithWebIdentityResult object, where the Credentials object contains the temporary credentials generated by MinIO:
AccessKeyId- The access key applications use for authentication.SecretAccessKey- The secret key applications use for authentication.Expiration- The RFC3339 date and time after which the credentials expire.SessionToken- Required with the access key and secret key when signing S3 requests with these temporary credentials.
The following example is similar to the response returned by the MinIO STS AssumeRoleWithWebIdentity endpoint:
Error Elements
The XML error response for this API endpoint is similar to the AWS AssumeRoleWithWebIdentity response.