Request Syntax Request Parameters Response Elements Errors See Also

UpdateTrustedTokenIssuer

Updates the name of the trusted token issuer, or the path of a source attribute or destination attribute for a trusted token issuer configuration.

Note

Updating this trusted token issuer configuration might cause users to lose access to any applications that are configured to use the trusted token issuer.

Request Syntax


{
   "Name": "string",
   "TrustedTokenIssuerArn": "string",
   "TrustedTokenIssuerConfiguration": { ... }
}

Request Parameters

For information about the parameters that are common to all actions, see Common Parameters.

The request accepts the following data in JSON format.

Name

Specifies the updated name to be applied to the trusted token issuer configuration.

Type: String

Length Constraints: Minimum length of 1. Maximum length of 255.

Pattern: ^[\w+=,.@-]+$

Required: No

TrustedTokenIssuerArn

Specifies the ARN of the trusted token issuer configuration that you want to update.

Type: String

Length Constraints: Minimum length of 10. Maximum length of 1224.

Pattern: ^arn:(aws|aws-us-gov|aws-cn|aws-iso|aws-iso-b):sso::\d{12}:trustedTokenIssuer/(sso)?ins-[a-zA-Z0-9-.]{16}/tti-[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}$

Required: Yes

TrustedTokenIssuerConfiguration

Specifies a structure with settings to apply to the specified trusted token issuer. The settings that you can provide are determined by the type of the trusted token issuer that you are updating.

Type: TrustedTokenIssuerUpdateConfiguration object

Note: This object is a Union. Only one member of this object can be specified or returned.

Required: No

Response Elements

If the action is successful, the service sends back an HTTP 200 response with an empty HTTP body.

Errors

For information about the errors that are common to all actions, see Common Errors.

AccessDeniedException

You do not have sufficient access to perform this action.

HTTP Status Code: 400

ConflictException

Occurs when a conflict with a previous successful write is detected. This generally occurs when the previous write did not have time to propagate to the host serving the current request. A retry (with appropriate backoff logic) is the recommended response to this exception.

HTTP Status Code: 400

InternalServerException

The request processing has failed because of an unknown error, exception, or failure with an internal server.

HTTP Status Code: 500

ResourceNotFoundException

Indicates that a requested resource is not found.

HTTP Status Code: 400

ThrottlingException

Indicates that the principal has crossed the throttling limits of the API operations.

HTTP Status Code: 400

ValidationException

The request failed because it contains a syntax error.

HTTP Status Code: 400