//
// Copyright 2010-2023 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.
//
#import "AWSCognitoIdentityProviderResources.h"
#import Adds additional user attributes to the user pool schema. Adds the specified user to the specified group. Calling this action requires developer credentials. Confirms user registration as an admin without using a confirmation code. Works on any user. Calling this action requires developer credentials. Creates a new user in the specified user pool. If This action might generate an SMS text message. Starting June 1, 2021, US telecom carriers require you to register an origination phone number before you can send SMS messages to US phone numbers. If you use SMS text messages in Amazon Cognito, you must register a phone number with Amazon Pinpoint. Amazon Cognito uses the registered number automatically. Otherwise, Amazon Cognito users who must receive SMS messages might not be able to sign up, activate their accounts, or sign in. If you have never used SMS text messages with Amazon Cognito or any other Amazon Web Service, Amazon Simple Notification Service might place your account in the SMS sandbox. In sandbox mode , you can send messages only to verified phone numbers. After you test your app while in the sandbox environment, you can move out of the sandbox and into production. For more information, see SMS message settings for Amazon Cognito user pools in the Amazon Cognito Developer Guide. This message is based on a template that you configured in your call to create or update a user pool. This template includes your custom sign-up instructions and placeholders for user name and temporary password. Alternatively, you can call In either case, the user will be in the Deletes a user as an administrator. Works on any user. Calling this action requires developer credentials. Deletes the user attributes in a user pool as an administrator. Works on any user. Calling this action requires developer credentials. Prevents the user from signing in with the specified external (SAML or social) identity provider (IdP). If the user that you want to deactivate is a Amazon Cognito user pools native username + password user, they can't use their password to sign in. If the user to deactivate is a linked external IdP user, any link between that user and an existing user is removed. When the external user signs in again, and the user is no longer attached to the previously linked This action is enabled only for admin access and requires developer credentials. The To deactivate a native username + password user, the The For de-linking a SAML identity, there are two scenarios. If the linked identity has not yet been used to sign in, the Deactivates a user and revokes all access tokens for the user. A deactivated user can't sign in, but still appears in the responses to You must make this API request with Amazon Web Services credentials that have Enables the specified user as an administrator. Works on any user. Calling this action requires developer credentials. Forgets the device, as an administrator. Calling this action requires developer credentials. Gets the device, as an administrator. Calling this action requires developer credentials. Gets the specified user by user name in a user pool as an administrator. Works on any user. Calling this action requires developer credentials. Initiates the authentication flow, as an administrator. This action might generate an SMS text message. Starting June 1, 2021, US telecom carriers require you to register an origination phone number before you can send SMS messages to US phone numbers. If you use SMS text messages in Amazon Cognito, you must register a phone number with Amazon Pinpoint. Amazon Cognito uses the registered number automatically. Otherwise, Amazon Cognito users who must receive SMS messages might not be able to sign up, activate their accounts, or sign in. If you have never used SMS text messages with Amazon Cognito or any other Amazon Web Service, Amazon Simple Notification Service might place your account in the SMS sandbox. In sandbox mode , you can send messages only to verified phone numbers. After you test your app while in the sandbox environment, you can move out of the sandbox and into production. For more information, see SMS message settings for Amazon Cognito user pools in the Amazon Cognito Developer Guide. Calling this action requires developer credentials. Links an existing user account in a user pool ( For example, if there is an existing user with a username and password, this API links that user to a federated user identity. When the user signs in with a federated user identity, they sign in as the existing user account. The maximum number of federated identities linked to a user is five. Because this API allows a user with an external federated identity to sign in as an existing user in the user pool, it is critical that it only be used with external IdPs and provider attributes that have been trusted by the application owner. This action is administrative and requires developer credentials. Lists devices, as an administrator. Calling this action requires developer credentials. Lists the groups that the user belongs to. Calling this action requires developer credentials. A history of user activity and any risks detected as part of Amazon Cognito advanced security. Removes the specified user from the specified group. Calling this action requires developer credentials. Resets the specified user's password in a user pool as an administrator. Works on any user. When a developer calls this API, the current password is invalidated, so it must be changed. If a user tries to sign in after the API is called, the app will get a PasswordResetRequiredException exception back and should direct the user down the flow to reset the password, which is the same as the forgot password flow. In addition, if the user pool has phone verification selected and a verified phone number exists for the user, or if email verification is selected and a verified email exists for the user, calling this API will also result in sending a message to the end user with the code to change their password. This action might generate an SMS text message. Starting June 1, 2021, US telecom carriers require you to register an origination phone number before you can send SMS messages to US phone numbers. If you use SMS text messages in Amazon Cognito, you must register a phone number with Amazon Pinpoint. Amazon Cognito uses the registered number automatically. Otherwise, Amazon Cognito users who must receive SMS messages might not be able to sign up, activate their accounts, or sign in. If you have never used SMS text messages with Amazon Cognito or any other Amazon Web Service, Amazon Simple Notification Service might place your account in the SMS sandbox. In sandbox mode , you can send messages only to verified phone numbers. After you test your app while in the sandbox environment, you can move out of the sandbox and into production. For more information, see SMS message settings for Amazon Cognito user pools in the Amazon Cognito Developer Guide. Calling this action requires developer credentials. Responds to an authentication challenge, as an administrator. This action might generate an SMS text message. Starting June 1, 2021, US telecom carriers require you to register an origination phone number before you can send SMS messages to US phone numbers. If you use SMS text messages in Amazon Cognito, you must register a phone number with Amazon Pinpoint. Amazon Cognito uses the registered number automatically. Otherwise, Amazon Cognito users who must receive SMS messages might not be able to sign up, activate their accounts, or sign in. If you have never used SMS text messages with Amazon Cognito or any other Amazon Web Service, Amazon Simple Notification Service might place your account in the SMS sandbox. In sandbox mode , you can send messages only to verified phone numbers. After you test your app while in the sandbox environment, you can move out of the sandbox and into production. For more information, see SMS message settings for Amazon Cognito user pools in the Amazon Cognito Developer Guide. Calling this action requires developer credentials. The user's multi-factor authentication (MFA) preference, including which MFA options are activated, and if any are preferred. Only one factor can be set as preferred. The preferred MFA factor will be used to authenticate a user if multiple factors are activated. If multiple options are activated and no preference is set, a challenge to choose an MFA option will be returned during sign-in. Sets the specified user's password in a user pool as an administrator. Works on any user. The password can be temporary or permanent. If it is temporary, the user status enters the Once the user has set a new password, or the password is permanent, the user status is set to This action is no longer supported. You can use it to configure only SMS MFA. You can't use it to configure time-based one-time password (TOTP) software token MFA. To configure either type of MFA, use AdminSetUserMFAPreference instead. Provides feedback for an authentication event indicating if it was from a valid user. This feedback is used for improving the risk evaluation decision for the user pool as part of Amazon Cognito advanced security. Updates the device status as an administrator. Calling this action requires developer credentials. Updates the specified user's attributes, including developer attributes, as an administrator. Works on any user. For custom attributes, you must prepend the In addition to updating user attributes, this API can also be used to mark phone and email as verified. This action might generate an SMS text message. Starting June 1, 2021, US telecom carriers require you to register an origination phone number before you can send SMS messages to US phone numbers. If you use SMS text messages in Amazon Cognito, you must register a phone number with Amazon Pinpoint. Amazon Cognito uses the registered number automatically. Otherwise, Amazon Cognito users who must receive SMS messages might not be able to sign up, activate their accounts, or sign in. If you have never used SMS text messages with Amazon Cognito or any other Amazon Web Service, Amazon Simple Notification Service might place your account in the SMS sandbox. In sandbox mode , you can send messages only to verified phone numbers. After you test your app while in the sandbox environment, you can move out of the sandbox and into production. For more information, see SMS message settings for Amazon Cognito user pools in the Amazon Cognito Developer Guide. Calling this action requires developer credentials. Signs out a user from all devices. You must sign Calling this action requires developer credentials. Begins setup of time-based one-time password (TOTP) multi-factor authentication (MFA) for a user, with a unique private key that Amazon Cognito generates and returns in the API response. You can authorize an Amazon Cognito disassociates an existing software token when you verify the new token in a VerifySoftwareToken API request. If you don't verify the software token and your user pool doesn't require MFA, the user can then authenticate with user name and password credentials alone. If your user pool requires TOTP MFA, Amazon Cognito generates an After you set up software token MFA for your user, Amazon Cognito generates a Changes the password for a specified user in a user pool. Confirms tracking of the device. This API call is the call that begins device tracking. Allows a user to enter a confirmation code to reset a forgotten password. Confirms registration of a new user. Creates a new group in the specified user pool. Calling this action requires developer credentials. Creates an IdP for a user pool. Creates a new OAuth2.0 resource server and defines custom scopes within it. Creates the user import job. Creates a new Amazon Cognito user pool and sets the password policy for the pool. This action might generate an SMS text message. Starting June 1, 2021, US telecom carriers require you to register an origination phone number before you can send SMS messages to US phone numbers. If you use SMS text messages in Amazon Cognito, you must register a phone number with Amazon Pinpoint. Amazon Cognito uses the registered number automatically. Otherwise, Amazon Cognito users who must receive SMS messages might not be able to sign up, activate their accounts, or sign in. If you have never used SMS text messages with Amazon Cognito or any other Amazon Web Service, Amazon Simple Notification Service might place your account in the SMS sandbox. In sandbox mode , you can send messages only to verified phone numbers. After you test your app while in the sandbox environment, you can move out of the sandbox and into production. For more information, see SMS message settings for Amazon Cognito user pools in the Amazon Cognito Developer Guide. Creates the user pool client. When you create a new user pool client, token revocation is automatically activated. For more information about revoking tokens, see RevokeToken. Creates a new domain for a user pool. Deletes a group. Calling this action requires developer credentials. Deletes an IdP for a user pool. Deletes a resource server. Allows a user to delete himself or herself. Deletes the attributes for a user. Deletes the specified Amazon Cognito user pool. Allows the developer to delete the user pool client. Deletes a domain for a user pool. Gets information about a specific IdP. Describes a resource server. Describes the risk configuration. Describes the user import job. Returns the configuration information and metadata of the specified user pool. Client method for returning the configuration information and metadata of the specified user pool app client. Gets information about a domain. Forgets the specified device. Calling this API causes a message to be sent to the end user with a confirmation code that is required to change the user's password. For the This action might generate an SMS text message. Starting June 1, 2021, US telecom carriers require you to register an origination phone number before you can send SMS messages to US phone numbers. If you use SMS text messages in Amazon Cognito, you must register a phone number with Amazon Pinpoint. Amazon Cognito uses the registered number automatically. Otherwise, Amazon Cognito users who must receive SMS messages might not be able to sign up, activate their accounts, or sign in. If you have never used SMS text messages with Amazon Cognito or any other Amazon Web Service, Amazon Simple Notification Service might place your account in the SMS sandbox. In sandbox mode , you can send messages only to verified phone numbers. After you test your app while in the sandbox environment, you can move out of the sandbox and into production. For more information, see SMS message settings for Amazon Cognito user pools in the Amazon Cognito Developer Guide. Gets the header information for the comma-separated value (CSV) file to be used as input for the user import job. Gets the device. Gets a group. Calling this action requires developer credentials. Gets the specified IdP. This method takes a user pool ID, and returns the signing certificate. The issued certificate is valid for 10 years from the date of issue. Amazon Cognito issues and assigns a new signing certificate annually. This process returns a new value in the response to Gets the user interface (UI) Customization information for a particular app client's app UI, if any such information exists for the client. If nothing is set for the particular client, but there is an existing pool level customization (the app Gets the user attributes and metadata for a user. Generates a user attribute verification code for the specified attribute name. Sends a message to a user with a code that they must return in a VerifyUserAttribute request. This action might generate an SMS text message. Starting June 1, 2021, US telecom carriers require you to register an origination phone number before you can send SMS messages to US phone numbers. If you use SMS text messages in Amazon Cognito, you must register a phone number with Amazon Pinpoint. Amazon Cognito uses the registered number automatically. Otherwise, Amazon Cognito users who must receive SMS messages might not be able to sign up, activate their accounts, or sign in. If you have never used SMS text messages with Amazon Cognito or any other Amazon Web Service, Amazon Simple Notification Service might place your account in the SMS sandbox. In sandbox mode , you can send messages only to verified phone numbers. After you test your app while in the sandbox environment, you can move out of the sandbox and into production. For more information, see SMS message settings for Amazon Cognito user pools in the Amazon Cognito Developer Guide. Gets the user pool multi-factor authentication (MFA) configuration. Signs out users from all devices. It also invalidates all refresh tokens that Amazon Cognito has issued to a user. A user can still use a hosted UI cookie to retrieve new tokens for the duration of the 1-hour cookie validity period. Initiates sign-in for a user in the Amazon Cognito user directory. You can't sign in a user with a federated IdP with This action might generate an SMS text message. Starting June 1, 2021, US telecom carriers require you to register an origination phone number before you can send SMS messages to US phone numbers. If you use SMS text messages in Amazon Cognito, you must register a phone number with Amazon Pinpoint. Amazon Cognito uses the registered number automatically. Otherwise, Amazon Cognito users who must receive SMS messages might not be able to sign up, activate their accounts, or sign in. If you have never used SMS text messages with Amazon Cognito or any other Amazon Web Service, Amazon Simple Notification Service might place your account in the SMS sandbox. In sandbox mode , you can send messages only to verified phone numbers. After you test your app while in the sandbox environment, you can move out of the sandbox and into production. For more information, see SMS message settings for Amazon Cognito user pools in the Amazon Cognito Developer Guide. Lists the sign-in devices that Amazon Cognito has registered to the current user. Lists the groups associated with a user pool. Calling this action requires developer credentials. Lists information about all IdPs for a user pool. Lists the resource servers for a user pool. Lists the tags that are assigned to an Amazon Cognito user pool. A tag is a label that you can apply to user pools to categorize and manage them in different ways, such as by purpose, owner, environment, or other criteria. You can use this action up to 10 times per second, per account. Lists the user import jobs. Lists the clients that have been created for the specified user pool. Lists the user pools associated with an Amazon Web Services account. Lists the users in the Amazon Cognito user pool. Lists the users in the specified group. Calling this action requires developer credentials. Resends the confirmation (for confirmation of registration) to a specific user in the user pool. This action might generate an SMS text message. Starting June 1, 2021, US telecom carriers require you to register an origination phone number before you can send SMS messages to US phone numbers. If you use SMS text messages in Amazon Cognito, you must register a phone number with Amazon Pinpoint. Amazon Cognito uses the registered number automatically. Otherwise, Amazon Cognito users who must receive SMS messages might not be able to sign up, activate their accounts, or sign in. If you have never used SMS text messages with Amazon Cognito or any other Amazon Web Service, Amazon Simple Notification Service might place your account in the SMS sandbox. In sandbox mode , you can send messages only to verified phone numbers. After you test your app while in the sandbox environment, you can move out of the sandbox and into production. For more information, see SMS message settings for Amazon Cognito user pools in the Amazon Cognito Developer Guide. Responds to the authentication challenge. This action might generate an SMS text message. Starting June 1, 2021, US telecom carriers require you to register an origination phone number before you can send SMS messages to US phone numbers. If you use SMS text messages in Amazon Cognito, you must register a phone number with Amazon Pinpoint. Amazon Cognito uses the registered number automatically. Otherwise, Amazon Cognito users who must receive SMS messages might not be able to sign up, activate their accounts, or sign in. If you have never used SMS text messages with Amazon Cognito or any other Amazon Web Service, Amazon Simple Notification Service might place your account in the SMS sandbox. In sandbox mode , you can send messages only to verified phone numbers. After you test your app while in the sandbox environment, you can move out of the sandbox and into production. For more information, see SMS message settings for Amazon Cognito user pools in the Amazon Cognito Developer Guide. Revokes all of the access tokens generated by, and at the same time as, the specified refresh token. After a token is revoked, you can't use the revoked token to access Amazon Cognito user APIs, or to authorize access to your resource server. Configures actions on detected risks. To delete the risk configuration for To activate Amazon Cognito advanced security features, update the user pool to include the Sets the user interface (UI) customization information for a user pool's built-in app UI. You can specify app UI customization settings for a single client (with a specific To use this API, your user pool must have a domain associated with it. Otherwise, there is no place to host the app's pages, and the service will throw an error. Set the user's multi-factor authentication (MFA) method preference, including which MFA factors are activated and if any are preferred. Only one factor can be set as preferred. The preferred MFA factor will be used to authenticate a user if multiple factors are activated. If multiple options are activated and no preference is set, a challenge to choose an MFA option will be returned during sign-in. If an MFA type is activated for a user, the user will be prompted for MFA during all sign-in attempts unless device tracking is turned on and the device has been trusted. If you want MFA to be applied selectively based on the assessed risk level of sign-in attempts, deactivate MFA for users and turn on Adaptive Authentication for the user pool. Sets the user pool multi-factor authentication (MFA) configuration. This action might generate an SMS text message. Starting June 1, 2021, US telecom carriers require you to register an origination phone number before you can send SMS messages to US phone numbers. If you use SMS text messages in Amazon Cognito, you must register a phone number with Amazon Pinpoint. Amazon Cognito uses the registered number automatically. Otherwise, Amazon Cognito users who must receive SMS messages might not be able to sign up, activate their accounts, or sign in. If you have never used SMS text messages with Amazon Cognito or any other Amazon Web Service, Amazon Simple Notification Service might place your account in the SMS sandbox. In sandbox mode , you can send messages only to verified phone numbers. After you test your app while in the sandbox environment, you can move out of the sandbox and into production. For more information, see SMS message settings for Amazon Cognito user pools in the Amazon Cognito Developer Guide. This action is no longer supported. You can use it to configure only SMS MFA. You can't use it to configure time-based one-time password (TOTP) software token MFA. To configure either type of MFA, use SetUserMFAPreference instead. Registers the user in the specified user pool and creates a user name, password, and user attributes. This action might generate an SMS text message. Starting June 1, 2021, US telecom carriers require you to register an origination phone number before you can send SMS messages to US phone numbers. If you use SMS text messages in Amazon Cognito, you must register a phone number with Amazon Pinpoint. Amazon Cognito uses the registered number automatically. Otherwise, Amazon Cognito users who must receive SMS messages might not be able to sign up, activate their accounts, or sign in. If you have never used SMS text messages with Amazon Cognito or any other Amazon Web Service, Amazon Simple Notification Service might place your account in the SMS sandbox. In sandbox mode , you can send messages only to verified phone numbers. After you test your app while in the sandbox environment, you can move out of the sandbox and into production. For more information, see SMS message settings for Amazon Cognito user pools in the Amazon Cognito Developer Guide. Starts the user import. Stops the user import job. Assigns a set of tags to an Amazon Cognito user pool. A tag is a label that you can use to categorize and manage user pools in different ways, such as by purpose, owner, environment, or other criteria. Each tag consists of a key and value, both of which you define. A key is a general category for more specific values. For example, if you have two versions of a user pool, one for testing and another for production, you might assign an Tags are useful for cost tracking and access control. You can activate your tags so that they appear on the Billing and Cost Management console, where you can track the costs associated with your user pools. In an Identity and Access Management policy, you can constrain permissions for user pools based on specific tags or tag values. You can use this action up to 5 times per second, per account. A user pool can have as many as 50 tags. Removes the specified tags from an Amazon Cognito user pool. You can use this action up to 5 times per second, per account. Provides the feedback for an authentication event, whether it was from a valid user or not. This feedback is used for improving the risk evaluation decision for the user pool as part of Amazon Cognito advanced security. Updates the device status. Updates the specified group with the specified attributes. Calling this action requires developer credentials. Updates IdP information for a user pool. Updates the name and scopes of resource server. All other fields are read-only. If you don't provide a value for an attribute, it is set to the default value. Allows a user to update a specific attribute (one at a time). This action might generate an SMS text message. Starting June 1, 2021, US telecom carriers require you to register an origination phone number before you can send SMS messages to US phone numbers. If you use SMS text messages in Amazon Cognito, you must register a phone number with Amazon Pinpoint. Amazon Cognito uses the registered number automatically. Otherwise, Amazon Cognito users who must receive SMS messages might not be able to sign up, activate their accounts, or sign in. If you have never used SMS text messages with Amazon Cognito or any other Amazon Web Service, Amazon Simple Notification Service might place your account in the SMS sandbox. In sandbox mode , you can send messages only to verified phone numbers. After you test your app while in the sandbox environment, you can move out of the sandbox and into production. For more information, see SMS message settings for Amazon Cognito user pools in the Amazon Cognito Developer Guide. Updates the specified user pool with the specified attributes. You can get a list of the current user pool settings using DescribeUserPool. If you don't provide a value for an attribute, it will be set to the default value. This action might generate an SMS text message. Starting June 1, 2021, US telecom carriers require you to register an origination phone number before you can send SMS messages to US phone numbers. If you use SMS text messages in Amazon Cognito, you must register a phone number with Amazon Pinpoint. Amazon Cognito uses the registered number automatically. Otherwise, Amazon Cognito users who must receive SMS messages might not be able to sign up, activate their accounts, or sign in. If you have never used SMS text messages with Amazon Cognito or any other Amazon Web Service, Amazon Simple Notification Service might place your account in the SMS sandbox. In sandbox mode , you can send messages only to verified phone numbers. After you test your app while in the sandbox environment, you can move out of the sandbox and into production. For more information, see SMS message settings for Amazon Cognito user pools in the Amazon Cognito Developer Guide. Updates the specified user pool app client with the specified attributes. You can get a list of the current user pool app client settings using DescribeUserPoolClient. If you don't provide a value for an attribute, it will be set to the default value. You can also use this operation to enable token revocation for user pool clients. For more information about revoking tokens, see RevokeToken. Updates the Secure Sockets Layer (SSL) certificate for the custom domain for your user pool. You can use this operation to provide the Amazon Resource Name (ARN) of a new certificate to Amazon Cognito. You can't use it to change the domain for a user pool. A custom domain is used to host the Amazon Cognito hosted UI, which provides sign-up and sign-in pages for your application. When you set up a custom domain, you provide a certificate that you manage with Certificate Manager (ACM). When necessary, you can use this operation to change the certificate that you applied to your custom domain. Usually, this is unnecessary following routine certificate renewal with ACM. When you renew your existing certificate in ACM, the ARN for your certificate remains the same, and your custom domain uses the new certificate automatically. However, if you replace your existing certificate with a new one, ACM gives the new certificate a new ARN. To apply the new certificate to your custom domain, you must provide this ARN to Amazon Cognito. When you add your new certificate in ACM, you must choose US East (N. Virginia) as the Amazon Web Services Region. After you submit your request, Amazon Cognito requires up to 1 hour to distribute your new certificate to your custom domain. For more information about adding a custom domain to your user pool, see Using Your Own Domain for the Hosted UI. Use this API to register a user's entered time-based one-time password (TOTP) code and mark the user's software token MFA status as \\\"verified\\\" if successful. The request takes an access token or a session string, but not both. Verifies the specified user attributes in the user pool. If your user pool requires verification before Amazon Cognito updates the attribute value, VerifyUserAttribute updates the affected attribute to its pending value. For more information, see UserAttributeUpdateSettingsType. The list of The data type for Flag specifying whether to send a notification. The action to take in response to the account takeover action. Valid values are as follows: Account takeover action type. Action to take for a low risk. Action to take for a medium risk. Action to take for a high risk. Account takeover actions type. The notify configuration used to construct email notifications. Account takeover risk configuration actions. Configuration for mitigation actions and notification for different levels of risk detected for a potential account takeover. The user pool ID for the user pool where you want to add custom attributes. An array of custom attributes, such as Mutable and Name. Represents the request to add custom attributes. Represents the response from the server for the request to add custom attributes. The user pool ID for the user pool. The username for the user. The group name. The user pool ID for which you want to confirm user registration. The user name for which you want to confirm user registration. A map of custom key-value pairs that you can provide as input for any custom workflows that this action triggers. If your user pool configuration includes triggers, the AdminConfirmSignUp API action invokes the Lambda function that is specified for the post confirmation trigger. When Amazon Cognito invokes this function, it passes a JSON payload, which the function receives as input. In this payload, the For more information, see Customizing user pool Workflows with Lambda Triggers in the Amazon Cognito Developer Guide. When you use the ClientMetadata parameter, remember that Amazon Cognito won't do the following: Store the ClientMetadata value. This data is available only to Lambda triggers that are assigned to a user pool to support custom workflows. If your user pool configuration doesn't include triggers, the ClientMetadata parameter serves no purpose. Validate the ClientMetadata value. Encrypt the ClientMetadata value. Don't use Amazon Cognito to provide sensitive information. Represents the request to confirm user registration. Represents the response from the server for the request to confirm registration. Set to The user account expiration limit, in days, after which a new account that hasn't signed in is no longer usable. To reset the account after that time limit, you must call If you set a value for The message template to be used for the welcome message to new users. See also Customizing User Invitation Messages. The configuration for creating a new user profile. The user pool ID for the user pool where the user will be created. The username for the user. Must be unique within the user pool. Must be a UTF-8 string between 1 and 128 characters. After the user is created, the username can't be changed. An array of name-value pairs that contain user attributes and attribute values to be set for the user to be created. You can create a user without specifying any attributes other than For custom attributes, you must prepend the To send a message inviting the user to sign up, you must specify the user's email address or phone number. You can do this in your call to AdminCreateUser or in the Users tab of the Amazon Cognito console for managing your user pools. In your call to email: The email address of the user to whom the message that contains the code and username will be sent. Required if the phone_number: The phone number of the user to whom the message that contains the code and username will be sent. Required if the The user's validation data. This is an array of name-value pairs that contain user attributes and attribute values that you can use for custom validation, such as restricting the types of user accounts that can be registered. For example, you might choose to allow or disallow user sign-up based on the user's domain. To configure custom validation, you must create a Pre Sign-up Lambda trigger for the user pool as described in the Amazon Cognito Developer Guide. The Lambda trigger receives the validation data and uses it in the validation process. The user's validation data isn't persisted. The user's temporary password. This password must conform to the password policy that you specified when you created the user pool. The temporary password is valid only once. To complete the Admin Create User flow, the user must enter the temporary password in the sign-in page, along with a new password to be used in all future sign-ins. This parameter isn't required. If you don't specify a value, Amazon Cognito generates one for you. The temporary password can only be used until the user account expiration limit that you specified when you created the user pool. To reset the account after that time limit, you must call This parameter is used only if the If this parameter is set to If this parameter is set to Set to Specify A map of custom key-value pairs that you can provide as input for any custom workflows that this action triggers. You create custom workflows by assigning Lambda functions to user pool triggers. When you use the AdminCreateUser API action, Amazon Cognito invokes the function that is assigned to the pre sign-up trigger. When Amazon Cognito invokes this function, it passes a JSON payload, which the function receives as input. This payload contains a For more information, see Customizing user pool Workflows with Lambda Triggers in the Amazon Cognito Developer Guide. When you use the ClientMetadata parameter, remember that Amazon Cognito won't do the following: Store the ClientMetadata value. This data is available only to Lambda triggers that are assigned to a user pool to support custom workflows. If your user pool configuration doesn't include triggers, the ClientMetadata parameter serves no purpose. Validate the ClientMetadata value. Encrypt the ClientMetadata value. Don't use Amazon Cognito to provide sensitive information. Represents the request to create a user in the specified user pool. The newly created user. Represents the response from the server to the request to create the user. The user pool ID for the user pool where you want to delete user attributes. The user name of the user from which you would like to delete attributes. An array of strings representing the user attribute names you want to delete. For custom attributes, you must prepend the Represents the request to delete user attributes as an administrator. Represents the response received from the server for a request to delete user attributes. The user pool ID for the user pool where you want to delete the user. The user name of the user you want to delete. Represents the request to delete a user as an administrator. The user pool ID for the user pool. The user to be disabled. The user pool ID for the user pool where you want to disable the user. The user name of the user you want to disable. Represents the request to disable the user as an administrator. Represents the response received from the server to disable the user as an administrator. The user pool ID for the user pool where you want to enable the user. The user name of the user you want to enable. Represents the request that enables the user as an administrator. Represents the response from the server for the request to enable a user as an administrator. The user pool ID. The user name. The device key. Sends the forgot device request, as an administrator. The device key. The user pool ID. The user name. Represents the request to get the device, as an administrator. The device. Gets the device response, as an administrator. The user pool ID for the user pool where you want to get information about the user. The user name of the user you want to retrieve. Represents the request to get the specified user as an administrator. The user name of the user about whom you're receiving information. An array of name-value pairs representing user attributes. The date the user was created. The date the user was last modified. Indicates that the status is The user status. Can be one of the following: UNCONFIRMED - User has been created but not confirmed. CONFIRMED - User has been confirmed. ARCHIVED - User is no longer active. UNKNOWN - User status isn't known. RESET_REQUIRED - User is confirmed, but the user must request a code and reset their password before they can sign in. FORCE_CHANGE_PASSWORD - The user is confirmed and the user can sign in using a temporary password, but on first sign-in, the user must change their password to a new value before doing anything else. This response parameter is no longer supported. It provides information only about SMS MFA configurations. It doesn't provide information about time-based one-time password (TOTP) software token MFA configurations. To look up information about either type of MFA configuration, use UserMFASettingList instead. The user's preferred MFA setting. The MFA options that are activated for the user. The possible values in this list are Represents the response from the server from the request to get the specified user as an administrator. The ID of the Amazon Cognito user pool. The app client ID. The authentication flow for this call to run. The API action will depend on this value. For example: Valid values include: The authentication parameters. These are inputs corresponding to the For For For For A map of custom key-value pairs that you can provide as input for certain custom workflows that this action triggers. You create custom workflows by assigning Lambda functions to user pool triggers. When you use the AdminInitiateAuth API action, Amazon Cognito invokes the Lambda functions that are specified for various triggers. The ClientMetadata value is passed as input to the functions for only the following triggers: Pre signup Pre authentication User migration When Amazon Cognito invokes the functions for these triggers, it passes a JSON payload, which the function receives as input. This payload contains a When you use the AdminInitiateAuth API action, Amazon Cognito also invokes the functions for the following triggers, but it doesn't provide the ClientMetadata value as input: Post authentication Custom message Pre token generation Create auth challenge Define auth challenge Verify auth challenge For more information, see Customizing user pool Workflows with Lambda Triggers in the Amazon Cognito Developer Guide. When you use the ClientMetadata parameter, remember that Amazon Cognito won't do the following: Store the ClientMetadata value. This data is available only to Lambda triggers that are assigned to a user pool to support custom workflows. If your user pool configuration doesn't include triggers, the ClientMetadata parameter serves no purpose. Validate the ClientMetadata value. Encrypt the ClientMetadata value. Don't use Amazon Cognito to provide sensitive information. The analytics metadata for collecting Amazon Pinpoint metrics for Contextual data about your user session, such as the device fingerprint, IP address, or location. Amazon Cognito advanced security evaluates the risk of an authentication event based on the context that your app generates and passes to Amazon Cognito when it makes API requests. Initiates the authorization request, as an administrator. The name of the challenge that you're responding to with this call. This is returned in the In a To set up software token MFA, use the session returned here from The session that should be passed both ways in challenge-response calls to the service. If The challenge parameters. These are returned to you in the All challenges require The value of the The result of the authentication response. This is only returned if the caller doesn't need to pass another challenge. If the caller does need to pass another challenge before it gets tokens, Initiates the authentication response, as an administrator. The user pool ID for the user pool. The existing user in the user pool that you want to assign to the external IdP user account. This user can be a native (Username + Password) Amazon Cognito user pools user or a federated user (for example, a SAML or Facebook user). If the user doesn't exist, Amazon Cognito generates an exception. Amazon Cognito returns this user when the new user (with the linked IdP attribute) signs in. For a native username + password user, the The The All attributes in the DestinationUser profile must be mutable. If you have assigned the user any immutable custom attributes, the operation won't succeed. An external IdP account for a user who doesn't exist yet in the user pool. This user must be a federated user (for example, a SAML or Facebook user), not another native user. If the For SAML, the The user pool ID. The user name. The limit of the devices request. The pagination token. Represents the request to list devices, as an administrator. The devices in the list of devices response. The pagination token. Lists the device's response, as an administrator. The username for the user. The user pool ID for the user pool. The limit of the request to list groups. An identifier that was returned from the previous call to this operation, which can be used to return the next set of items in the list. The groups that the user belongs to. An identifier that was returned from the previous call to this operation, which can be used to return the next set of items in the list. The user pool ID. The user pool username or an alias. The maximum number of authentication events to return. Returns 60 events if you set A pagination token. The response object. It includes the A pagination token. The user pool ID for the user pool. The username for the user. The group name. The user pool ID for the user pool where you want to reset the user's password. The user name of the user whose password you want to reset. A map of custom key-value pairs that you can provide as input for any custom workflows that this action triggers. You create custom workflows by assigning Lambda functions to user pool triggers. When you use the AdminResetUserPassword API action, Amazon Cognito invokes the function that is assigned to the custom message trigger. When Amazon Cognito invokes this function, it passes a JSON payload, which the function receives as input. This payload contains a For more information, see Customizing user pool Workflows with Lambda Triggers in the Amazon Cognito Developer Guide. When you use the ClientMetadata parameter, remember that Amazon Cognito won't do the following: Store the ClientMetadata value. This data is available only to Lambda triggers that are assigned to a user pool to support custom workflows. If your user pool configuration doesn't include triggers, the ClientMetadata parameter serves no purpose. Validate the ClientMetadata value. Encrypt the ClientMetadata value. Don't use Amazon Cognito to provide sensitive information. Represents the request to reset a user's password as an administrator. Represents the response from the server to reset a user password as an administrator. The ID of the Amazon Cognito user pool. The app client ID. The challenge name. For more information, see AdminInitiateAuth. The challenge responses. These are inputs corresponding to the value of In a The value of the The session that should be passed both ways in challenge-response calls to the service. If an The analytics metadata for collecting Amazon Pinpoint metrics for Contextual data about your user session, such as the device fingerprint, IP address, or location. Amazon Cognito advanced security evaluates the risk of an authentication event based on the context that your app generates and passes to Amazon Cognito when it makes API requests. A map of custom key-value pairs that you can provide as input for any custom workflows that this action triggers. You create custom workflows by assigning Lambda functions to user pool triggers. When you use the AdminRespondToAuthChallenge API action, Amazon Cognito invokes any functions that you have assigned to the following triggers: pre sign-up custom message post authentication user migration pre token generation define auth challenge create auth challenge verify auth challenge response When Amazon Cognito invokes any of these functions, it passes a JSON payload, which the function receives as input. This payload contains a For more information, see Customizing user pool Workflows with Lambda Triggers in the Amazon Cognito Developer Guide. When you use the ClientMetadata parameter, remember that Amazon Cognito won't do the following: Store the ClientMetadata value. This data is available only to Lambda triggers that are assigned to a user pool to support custom workflows. If your user pool configuration doesn't include triggers, the ClientMetadata parameter serves no purpose. Validate the ClientMetadata value. Encrypt the ClientMetadata value. Don't use Amazon Cognito to provide sensitive information. The request to respond to the authentication challenge, as an administrator. The name of the challenge. For more information, see AdminInitiateAuth. The session that should be passed both ways in challenge-response calls to the service. If the caller must pass another challenge, they return a session with other challenge parameters. This session should be passed as it is to the next The challenge parameters. For more information, see AdminInitiateAuth. The result returned by the server in response to the authentication request. Responds to the authentication challenge, as an administrator. The SMS text message MFA settings. The time-based one-time password software token MFA settings. The user pool username or alias. The user pool ID. The user pool ID for the user pool where you want to set the user's password. The user name of the user whose password you want to set. The password for the user. The ID of the user pool that contains the user whose options you're setting. The user name of the user whose options you're setting. You can use this parameter only to set an SMS configuration that uses SMS for delivery. You can use this parameter to set an MFA configuration that uses the SMS delivery medium. Represents the response from the server to set user settings as an administrator. The user pool ID. The user pool username. The authentication event ID. The authentication event feedback value. The user pool ID. The user name. The device key. The status indicating whether a device has been remembered or not. The request to update the device status, as an administrator. The status response to the request to update the device, as an administrator. The user pool ID for the user pool where you want to update user attributes. The user name of the user for whom you want to update user attributes. An array of name-value pairs representing user attributes. For custom attributes, you must prepend the If your user pool requires verification before Amazon Cognito updates an attribute value that you specify in this request, Amazon Cognito doesnât immediately update the value of that attribute. After your user receives and responds to a verification message to verify the new value, Amazon Cognito updates the attribute value. Your user can sign in and receive messages with the original attribute value until they verify the new value. To update the value of an attribute that requires verification in the same API request, include the A map of custom key-value pairs that you can provide as input for any custom workflows that this action triggers. You create custom workflows by assigning Lambda functions to user pool triggers. When you use the AdminUpdateUserAttributes API action, Amazon Cognito invokes the function that is assigned to the custom message trigger. When Amazon Cognito invokes this function, it passes a JSON payload, which the function receives as input. This payload contains a For more information, see Customizing user pool Workflows with Lambda Triggers in the Amazon Cognito Developer Guide. When you use the ClientMetadata parameter, remember that Amazon Cognito won't do the following: Store the ClientMetadata value. This data is available only to Lambda triggers that are assigned to a user pool to support custom workflows. If your user pool configuration doesn't include triggers, the ClientMetadata parameter serves no purpose. Validate the ClientMetadata value. Encrypt the ClientMetadata value. Don't use Amazon Cognito to provide sensitive information. Represents the request to update the user's attributes as an administrator. Represents the response from the server for the request to update user attributes as an administrator. The user pool ID. The user name. The request to sign out of all devices, as an administrator. The global sign-out response, as an administrator. The message that Amazon Cognito sends to the user when the value of an alias attribute is already linked to another user profile. This exception is thrown when a user tries to confirm the account with an email address or phone number that has already been supplied as an alias for a different user profile. This exception indicates that an account with this email address or phone already exists in a user pool that you've configured to use email address or phone number as a sign-in alias. The application ID for an Amazon Pinpoint application. The Amazon Resource Name (ARN) of an Amazon Pinpoint project. You can use the Amazon Pinpoint project to integrate with the chosen user pool Client. Amazon Cognito publishes events to the Amazon Pinpoint project that the app ARN declares. The ARN of an Identity and Access Management role that authorizes Amazon Cognito to publish events to Amazon Pinpoint analytics. The external ID. If The Amazon Pinpoint analytics configuration necessary to collect metrics for a user pool. In Regions where Amazon Pinpointisn't available, user pools only support sending events to Amazon Pinpoint projects in us-east-1. In Regions where Amazon Pinpoint is available, user pools support sending events to Amazon Pinpoint projects within that same Region. The endpoint ID. An Amazon Pinpoint analytics endpoint. An endpoint uniquely identifies a mobile device, email address, or phone number that can receive messages from Amazon Pinpoint analytics. For more information about Amazon Web Services Regions that can contain Amazon Pinpoint resources for use with Amazon Cognito user pools, see Using Amazon Pinpoint analytics with Amazon Cognito user pools. A valid access token that Amazon Cognito issued to the user whose software token you want to generate. The session that should be passed both ways in challenge-response calls to the service. This allows authentication of the user as part of the MFA setup process. A unique generated shared secret code that is used in the TOTP algorithm to generate a one-time code. The session that should be passed both ways in challenge-response calls to the service. This allows authentication of the user as part of the MFA setup process. The name of the attribute. The value of the attribute. Specifies whether the attribute is standard or custom. The event ID. The event type. The creation date The event response. The event risk. The challenge responses. The user context data captured at the time of an event request. This value provides additional information about the client from which event the request is received. A flag specifying the user feedback captured at the time of an event request is good or bad. The authentication event type. A valid access token that Amazon Cognito issued to the user who you want to authenticate. The expiration period of the authentication result in seconds. The token type. The refresh token. The ID token. The new device metadata from an authentication result. The authentication result. The challenge name. The challenge response. The challenge response type. The old password. The new password. A valid access token that Amazon Cognito issued to the user whose password you want to change. Represents the request to change a user password. The response from the server to the change password request. The email address or phone number destination where Amazon Cognito sent the code. The method that Amazon Cognito used to send the code. The name of the attribute that Amazon Cognito verifies with the code. The delivery details for an email or SMS message that Amazon Cognito sent for authentication or verification. The message sent when a verification code fails to deliver successfully. This exception is thrown when a verification code fails to deliver successfully. The message provided when the code mismatch exception is thrown. This exception is thrown if the provided code doesn't match what the server was expecting. The event action. The compromised credentials actions type. Perform the action for these events. The default is to perform all events if no event filter is specified. The compromised credentials risk configuration actions. The compromised credentials risk configuration type. The message provided when the concurrent exception is thrown. This exception is thrown if two or more modifications are happening concurrently. A valid access token that Amazon Cognito issued to the user whose device you want to confirm. The device key. The configuration of the device secret verifier. The device name. Confirms the device request. Indicates whether the user confirmation must confirm the device response. Confirms the device response. The app client ID of the app associated with the user pool. A keyed-hash message authentication code (HMAC) calculated using the secret key of a user pool client and username plus the client ID in the message. The user name of the user for whom you want to enter a code to retrieve a forgotten password. The confirmation code from your user's request to reset their password. For more information, see ForgotPassword. The new password that your user wants to set. The Amazon Pinpoint analytics metadata for collecting metrics for Contextual data about your user session, such as the device fingerprint, IP address, or location. Amazon Cognito advanced security evaluates the risk of an authentication event based on the context that your app generates and passes to Amazon Cognito when it makes API requests. A map of custom key-value pairs that you can provide as input for any custom workflows that this action triggers. You create custom workflows by assigning Lambda functions to user pool triggers. When you use the ConfirmForgotPassword API action, Amazon Cognito invokes the function that is assigned to the post confirmation trigger. When Amazon Cognito invokes this function, it passes a JSON payload, which the function receives as input. This payload contains a For more information, see Customizing user pool Workflows with Lambda Triggers in the Amazon Cognito Developer Guide. When you use the ClientMetadata parameter, remember that Amazon Cognito won't do the following: Store the ClientMetadata value. This data is available only to Lambda triggers that are assigned to a user pool to support custom workflows. If your user pool configuration doesn't include triggers, the ClientMetadata parameter serves no purpose. Validate the ClientMetadata value. Encrypt the ClientMetadata value. Don't use Amazon Cognito to provide sensitive information. The request representing the confirmation for a password reset. The response from the server that results from a user's request to retrieve a forgotten password. The ID of the app client associated with the user pool. A keyed-hash message authentication code (HMAC) calculated using the secret key of a user pool client and username plus the client ID in the message. The user name of the user whose registration you want to confirm. The confirmation code sent by a user's request to confirm registration. Boolean to be specified to force user confirmation irrespective of existing alias. By default set to The Amazon Pinpoint analytics metadata for collecting metrics for Contextual data about your user session, such as the device fingerprint, IP address, or location. Amazon Cognito advanced security evaluates the risk of an authentication event based on the context that your app generates and passes to Amazon Cognito when it makes API requests. A map of custom key-value pairs that you can provide as input for any custom workflows that this action triggers. You create custom workflows by assigning Lambda functions to user pool triggers. When you use the ConfirmSignUp API action, Amazon Cognito invokes the function that is assigned to the post confirmation trigger. When Amazon Cognito invokes this function, it passes a JSON payload, which the function receives as input. This payload contains a For more information, see Customizing user pool Workflows with Lambda Triggers in the Amazon Cognito Developer Guide. When you use the ClientMetadata parameter, remember that Amazon Cognito won't do the following: Store the ClientMetadata value. This data is available only to Lambda triggers that are assigned to a user pool to support custom workflows. If your user pool configuration doesn't include triggers, the ClientMetadata parameter serves no purpose. Validate the ClientMetadata value. Encrypt the ClientMetadata value. Don't use Amazon Cognito to provide sensitive information. Represents the request to confirm registration of a user. Represents the response from the server for the registration confirmation. The source IP address of your user's device. Your server endpoint where this API is invoked. Your server path where this API is invoked. HttpHeaders received on your server in same order. Encoded device-fingerprint details that your app collected with the Amazon Cognito context data collection library. For more information, see Adding user device and session data to API requests. Contextual user data type used for evaluating the risk of an unexpected event by Amazon Cognito advanced security. The name of the group. Must be unique. The user pool ID for the user pool. A string containing the description of the group. The role Amazon Resource Name (ARN) for the group. A non-negative integer value that specifies the precedence of this group relative to the other groups that a user can belong to in the user pool. Zero is the highest precedence value. Groups with lower Two groups can have the same The default The group object for the group. The user pool ID. The IdP name. The IdP type. The IdP details. The following list describes the provider detail keys for each IdP type. For Google and Login with Amazon: client_id client_secret authorize_scopes For Facebook: client_id client_secret authorize_scopes api_version For Sign in with Apple: client_id team_id key_id private_key authorize_scopes For OpenID Connect (OIDC) providers: client_id client_secret attributes_request_method oidc_issuer authorize_scopes The following keys are only present if Amazon Cognito didn't discover them at the authorize_url token_url attributes_url jwks_uri Amazon Cognito sets the value of the following keys automatically. They are read-only. attributes_url_add_attributes For SAML providers: MetadataFile or MetadataURL IDPSignout optional A mapping of IdP attributes to standard and custom user pool attributes. A list of IdP identifiers. The newly created IdP object. The user pool ID for the user pool. A unique resource server identifier for the resource server. This could be an HTTPS endpoint where the resource server is located, such as A friendly name for the resource server. A list of scopes. Each scope is a key-value map with the keys The newly created resource server. The job name for the user import job. The user pool ID for the user pool that the users are being imported into. The role ARN for the Amazon CloudWatch Logs Logging role for the user import job. Represents the request to create the user import job. The job object that represents the user import job. Represents the response from the server to the request to create the user import job. The user pool ID for the user pool where you want to create a user pool client. The client name for the user pool client you would like to create. Boolean to specify whether you want to generate a secret for the user pool client being created. The refresh token time limit. After this limit expires, your user can't use their refresh token. To specify the time unit for For example, when you set The default time unit for If you don't specify otherwise in the configuration of your app client, your refresh tokens are valid for 30 days. The access token time limit. After this limit expires, your user can't use their access token. To specify the time unit for For example, when you set The default time unit for If you don't specify otherwise in the configuration of your app client, your access tokens are valid for one hour. The ID token time limit. After this limit expires, your user can't use their ID token. To specify the time unit for For example, when you set The default time unit for If you don't specify otherwise in the configuration of your app client, your ID tokens are valid for one hour. The units in which the validity times are represented. The default unit for RefreshToken is days, and default for ID and access tokens are hours. The read attributes. The user pool attributes that the app client can write to. If your app client allows users to sign in through an IdP, this array must include all attributes that you have mapped to IdP attributes. Amazon Cognito updates mapped attributes when users sign in to your application through an IdP. If your app client does not have write access to a mapped attribute, Amazon Cognito throws an error when it tries to update the attribute. For more information, see Specifying IdP Attribute Mappings for Your user pool. The authentication flows that you want your user pool client to support. For each app client in your user pool, you can sign in your users with any combination of one or more flows, including with a user name and Secure Remote Password (SRP), a user name and password, or a custom authentication process that you define with Lambda functions. If you don't specify a value for Valid values include: In some environments, you will see the values A list of provider names for the identity providers (IdPs) that are supported on this client. The following are supported: A list of allowed redirect (callback) URLs for the IdPs. A redirect URI must: Be an absolute URI. Be registered with the authorization server. Not include a fragment component. See OAuth 2.0 - Redirection Endpoint. Amazon Cognito requires HTTPS over HTTP except for http://localhost for testing purposes only. App callback URLs such as myapp://example are also supported. A list of allowed logout URLs for the IdPs. The default redirect URI. Must be in the A redirect URI must: Be an absolute URI. Be registered with the authorization server. Not include a fragment component. See OAuth 2.0 - Redirection Endpoint. Amazon Cognito requires HTTPS over HTTP except for http://localhost for testing purposes only. App callback URLs such as myapp://example are also supported. The allowed OAuth flows. Use a code grant flow, which provides an authorization code as the response. This code can be exchanged for access tokens with the Issue the access token (and, optionally, ID token, based on scopes) directly to your user. Issue the access token from the The allowed OAuth scopes. Possible values provided by OAuth are Set to true if the client is allowed to follow the OAuth protocol when interacting with Amazon Cognito user pools. The user pool analytics configuration for collecting metrics and sending them to your Amazon Pinpoint campaign. In Amazon Web Services Regions where Amazon Pinpoint isn't available, user pools only support sending events to Amazon Pinpoint projects in Amazon Web Services Region us-east-1. In Regions where Amazon Pinpoint is available, user pools support sending events to Amazon Pinpoint projects within that same Region. Errors and responses that you want Amazon Cognito APIs to return during authentication, account confirmation, and password recovery when the user doesn't exist in the user pool. When set to Valid values include: Activates or deactivates token revocation. For more information about revoking tokens, see RevokeToken. If you don't include this parameter, token revocation is automatically activated for the new user pool client. Activates the propagation of additional user context data. For more information about propagation of user context data, see Adding advanced security to a user pool. If you donât include this parameter, you can't send device fingerprint information, including source IP address, to Amazon Cognito advanced security. You can only activate Amazon Cognito creates a session token for each API request in an authentication flow. Represents the request to create a user pool client. The user pool client that was just created. Represents the response from the server to create a user pool client. The domain string. For custom domains, this is the fully-qualified domain name, such as The user pool ID. The configuration for a custom domain that hosts the sign-up and sign-in webpages for your application. Provide this parameter only if you want to use a custom domain for your user pool. Otherwise, you can exclude this parameter and use the Amazon Cognito hosted domain instead. For more information about the hosted domain and custom domains, see Configuring a User Pool Domain. The Amazon CloudFront endpoint that you use as the target of the alias that you set up with your Domain Name Service (DNS) provider. A string used to name the user pool. The policies associated with the new user pool. When active, When you try to delete a protected user pool in a The Lambda trigger configuration information for the new user pool. In a push model, event sources (such as Amazon S3 and custom applications) need permission to invoke a function. So you must make an extra call to add permission for these event sources to invoke your Lambda function. For more information on using the Lambda API to add permission, see AddPermission . For adding permission using the CLI, see add-permission . The attributes to be auto-verified. Possible values: email, phone_number. Attributes supported as an alias for this user pool. Possible values: phone_number, email, or preferred_username. Specifies whether a user can use an email address or phone number as a username when they sign up. This parameter is no longer used. See VerificationMessageTemplateType. This parameter is no longer used. See VerificationMessageTemplateType. This parameter is no longer used. See VerificationMessageTemplateType. The template for the verification message that the user sees when the app requests permission to access the user's information. A string representing the SMS authentication message. Specifies MFA configuration details. The settings for updates to user attributes. These settings include the property The device-remembering configuration for a user pool. A null value indicates that you have deactivated device remembering in your user pool. When you provide a value for any The email configuration of your user pool. The email configuration type sets your preferred sending method, Amazon Web Services Region, and sender for messages from your user pool. The SMS configuration with the settings that your Amazon Cognito user pool must use to send an SMS message from your Amazon Web Services account through Amazon Simple Notification Service. To send SMS messages with Amazon SNS in the Amazon Web Services Region that you want, the Amazon Cognito user pool uses an Identity and Access Management (IAM) role in your Amazon Web Services account. The tag keys and values to assign to the user pool. A tag is a label that you can use to categorize and manage user pools in different ways, such as by purpose, owner, environment, or other criteria. The configuration for An array of schema attributes for the new user pool. These attributes can be standard or custom attributes. Enables advanced security risk detection. Set the key Case sensitivity on the username input for the selected sign-in option. For example, when case sensitivity is set to The available verified method a user can use to recover their password when they call Represents the request to create a user pool. A container for the user pool details. Represents the response from the server for the request to create a user pool. The Amazon Resource Name (ARN) of an Certificate Manager SSL certificate. You use this certificate for the subdomain of your custom domain. The configuration for a custom domain that hosts the sign-up and sign-in webpages for your application. Signature of the \\\"request\\\" attribute in the \\\"event\\\" information Amazon Cognito passes to your custom email Lambda function. The only supported value is The Amazon Resource Name (ARN) of the Lambda function that Amazon Cognito activates to send email notifications to users. A custom email sender Lambda configuration type. Signature of the \\\"request\\\" attribute in the \\\"event\\\" information that Amazon Cognito passes to your custom SMS Lambda function. The only supported value is The Amazon Resource Name (ARN) of the Lambda function that Amazon Cognito activates to send SMS notifications to users. A custom SMS sender Lambda configuration type. The name of the group. The user pool ID for the user pool. The user pool ID. The IdP name. The user pool ID for the user pool that hosts the resource server. The identifier for the resource server. An array of strings representing the user attribute names you want to delete. For custom attributes, you must prependattach the A valid access token that Amazon Cognito issued to the user whose attributes you want to delete. Represents the request to delete user attributes. Represents the response from the server to delete user attributes. The user pool ID for the user pool where you want to delete the client. The app client ID of the app associated with the user pool. Represents the request to delete a user pool client. The domain string. For custom domains, this is the fully-qualified domain name, such as The user pool ID. The user pool ID for the user pool you want to delete. Represents the request to delete a user pool. A valid access token that Amazon Cognito issued to the user whose user profile you want to delete. Represents the request to delete a user. The user pool ID. The IdP name. The identity provider details. The user pool ID for the user pool that hosts the resource server. The identifier for the resource server The resource server. The user pool ID. The app client ID. The risk configuration. The user pool ID for the user pool that the users are being imported into. The job ID for the user import job. Represents the request to describe the user import job. The job object that represents the user import job. Represents the response from the server to the request to describe the user import job. The user pool ID for the user pool you want to describe. The app client ID of the app associated with the user pool. Represents the request to describe a user pool client. The user pool client from a server response to describe the user pool client. Represents the response from the server from a request to describe the user pool client. The domain string. For custom domains, this is the fully-qualified domain name, such as A domain description object containing information about the domain. The user pool ID for the user pool you want to describe. Represents the request to describe the user pool. The container of metadata returned by the server to describe the pool. Represents the response to describe the user pool. When true, a remembered device can sign in with device authentication instead of SMS and time-based one-time password (TOTP) factors for multi-factor authentication (MFA). Whether or not When true, Amazon Cognito doesn't automatically remember a user's device when your app sends a ConfirmDevice API request. In your app, create a prompt for your user to choose whether they want to remember their device. Return the user's choice in an UpdateDeviceStatus API request. When The device-remembering configuration for a user pool. A DescribeUserPool request returns a null value for this object when the user pool isn't configured to remember devices. When device remembering is active, you can remember a user's device with a ConfirmDevice API request. Additionally. when the property To sign in with a remembered device, include When you provide a value for any property of The password verifier. The salt The device verifier against which it is authenticated. The device key. The device attributes. The creation date of the device. The last modified date of the device. The date when the device was last authenticated. The device type. The user pool ID. The Amazon Web Services ID for the user pool owner. The domain string. For custom domains, this is the fully-qualified domain name, such as The Amazon S3 bucket where the static files for this domain are stored. The Amazon Resource Name (ARN) of the Amazon CloudFront distribution. The app version. The domain status. The configuration for a custom domain that hosts the sign-up and sign-in webpages for your application. A container for information about a domain. This exception is thrown when the provider is already supported by the user pool. The ARN of a verified email address in Amazon SES. Amazon Cognito uses this email address in one of the following ways, depending on the value that you specify for the If you specify If you specify The Region value of the The destination to which the receiver of the email should reply. Specifies whether Amazon Cognito uses its built-in functionality to send your users email messages, or uses your Amazon Simple Email Service email configuration. Specify one of the following values: When Amazon Cognito emails your users, it uses its built-in email functionality. When you use the default option, Amazon Cognito allows only a limited number of emails each day for your user pool. For typical production environments, the default email limit is less than the required delivery volume. To achieve a higher delivery volume, specify DEVELOPER to use your Amazon SES email configuration. To look up the email delivery limit for the default option, see Limits in the Amazon Cognito Developer Guide. The default FROM address is When Amazon Cognito emails your users, it uses your Amazon SES configuration. Amazon Cognito calls Amazon SES on your behalf to send email from your verified email address. When you use this option, the email delivery limits are the same limits that apply to your Amazon SES verified email address in your Amazon Web Services account. If you use this option, provide the ARN of an Amazon SES verified email address for the Before Amazon Cognito can email your users, it requires additional permissions to call Amazon SES on your behalf. When you update your user pool with this option, Amazon Cognito creates a service-linked role, which is a type of role in your Amazon Web Services account. This role contains the permissions that allow you to access Amazon SES and send email messages from your email address. For more information about the service-linked role that Amazon Cognito creates, see Using Service-Linked Roles for Amazon Cognito in the Amazon Cognito Developer Guide. Either the senderâs email address or the senderâs name with their email address. For example, The set of configuration rules that can be applied to emails sent using Amazon Simple Email Service. A configuration set is applied to an email by including a reference to the configuration set in the headers of the email. Once applied, all of the rules in that configuration set are applied to the email. Configuration sets can be used to apply the following types of rules to emails: Amazon Simple Email Service can track the number of send, delivery, open, click, bounce, and complaint events for each email sent. Use event publishing to send information about these events to other Amazon Web Services services such as and Amazon CloudWatch When leasing dedicated IP addresses with Amazon Simple Email Service, you can create groups of IP addresses, called dedicated IP pools. You can then associate the dedicated IP pools with configuration sets. The email configuration of your user pool. The email configuration type sets your preferred sending method, Amazon Web Services Region, and sender for messages from your user pool. Amazon Cognito can send email messages with Amazon Simple Email Service resources in the Amazon Web Services Region where you created your user pool, and in alternate Regions in some cases. For more information on the supported Regions, see Email settings for Amazon Cognito user pools. This exception is thrown when there is a code mismatch and the service fails to configure the software token TOTP multi-factor authentication (MFA). The source IP address of your user's device. The user's device name. The user's time zone. The user's city. The user's country. Specifies the user context data captured at the time of an event request. The event feedback value. The provider. The event feedback date. Specifies the event feedback type. The risk decision. The risk level. Indicates whether compromised credentials were detected during an authentication event. The event risk type. The message returned when the expired code exception is thrown. This exception is thrown if a code has expired. The message returned when WAF doesn't allow your request based on a web ACL that's associated with your user pool. This exception is thrown when WAF doesn't allow your request based on a web ACL that's associated with your user pool. A valid access token that Amazon Cognito issued to the user whose registered device you want to forget. The device key. Represents the request to forget the device. The ID of the client associated with the user pool. A keyed-hash message authentication code (HMAC) calculated using the secret key of a user pool client and username plus the client ID in the message. Contextual data about your user session, such as the device fingerprint, IP address, or location. Amazon Cognito advanced security evaluates the risk of an authentication event based on the context that your app generates and passes to Amazon Cognito when it makes API requests. The user name of the user for whom you want to enter a code to reset a forgotten password. The Amazon Pinpoint analytics metadata that contributes to your metrics for A map of custom key-value pairs that you can provide as input for any custom workflows that this action triggers. You create custom workflows by assigning Lambda functions to user pool triggers. When you use the ForgotPassword API action, Amazon Cognito invokes any functions that are assigned to the following triggers: pre sign-up, custom message, and user migration. When Amazon Cognito invokes any of these functions, it passes a JSON payload, which the function receives as input. This payload contains a For more information, see Customizing user pool Workflows with Lambda Triggers in the Amazon Cognito Developer Guide. When you use the ClientMetadata parameter, remember that Amazon Cognito won't do the following: Store the ClientMetadata value. This data is available only to Lambda triggers that are assigned to a user pool to support custom workflows. If your user pool configuration doesn't include triggers, the ClientMetadata parameter serves no purpose. Validate the ClientMetadata value. Encrypt the ClientMetadata value. Don't use Amazon Cognito to provide sensitive information. Represents the request to reset a user's password. The code delivery details returned by the server in response to the request to reset a password. The response from Amazon Cognito to a request to reset a password. The user pool ID for the user pool that the users are to be imported into. Represents the request to get the header information of the CSV file for the user import job. The user pool ID for the user pool that the users are to be imported into. The header information of the CSV file for the user import job. Represents the response from the server to the request to get the header information of the CSV file for the user import job. The device key. A valid access token that Amazon Cognito issued to the user whose device information you want to request. Represents the request to get the device. The device. Gets the device response. The name of the group. The user pool ID for the user pool. The group object for the group. The user pool ID. The IdP identifier. The identity provider details. The user pool ID. Request to get a signing certificate from Amazon Cognito. The signing certificate. Response from Amazon Cognito for a signing certificate request. The user pool ID for the user pool. The client ID for the client app. The UI customization information. A non-expired access token for the user whose attribute verification code you want to generate. The attribute name returned by the server response to get the user attribute verification code. A map of custom key-value pairs that you can provide as input for any custom workflows that this action triggers. You create custom workflows by assigning Lambda functions to user pool triggers. When you use the GetUserAttributeVerificationCode API action, Amazon Cognito invokes the function that is assigned to the custom message trigger. When Amazon Cognito invokes this function, it passes a JSON payload, which the function receives as input. This payload contains a For more information, see Customizing user pool Workflows with Lambda Triggers in the Amazon Cognito Developer Guide. When you use the ClientMetadata parameter, remember that Amazon Cognito won't do the following: Store the ClientMetadata value. This data is available only to Lambda triggers that are assigned to a user pool to support custom workflows. If your user pool configuration doesn't include triggers, the ClientMetadata parameter serves no purpose. Validate the ClientMetadata value. Encrypt the ClientMetadata value. Don't use Amazon Cognito to provide sensitive information. Represents the request to get user attribute verification. The code delivery details returned by the server in response to the request to get the user attribute verification code. The verification code response returned by the server response to get the user attribute verification code. The user pool ID. The SMS text message multi-factor authentication (MFA) configuration. The software token multi-factor authentication (MFA) configuration. The multi-factor authentication (MFA) configuration. Valid values include: A non-expired access token for the user whose information you want to query. Represents the request to get information about the user. The user name of the user you want to retrieve from the get user request. An array of name-value pairs representing user attributes. For custom attributes, you must prepend the This response parameter is no longer supported. It provides information only about SMS MFA configurations. It doesn't provide information about time-based one-time password (TOTP) software token MFA configurations. To look up information about either type of MFA configuration, use UserMFASettingList instead. The user's preferred MFA setting. The MFA options that are activated for the user. The possible values in this list are Represents the response from the server from the request to get information about the user. A valid access token that Amazon Cognito issued to the user who you want to sign out. Represents the request to sign out all devices. The response to the request to sign out all devices. This exception is thrown when Amazon Cognito encounters a group that already exists in the user pool. The name of the group. The user pool ID for the user pool. A string containing the description of the group. The role Amazon Resource Name (ARN) for the group. A non-negative integer value that specifies the precedence of this group relative to the other groups that a user can belong to in the user pool. Zero is the highest precedence value. Groups with lower Two groups can have the same The default The date the group was last modified. The date the group was created. The group type. The header name. The header value. The HTTP header. The user pool ID. The IdP name. The IdP type. The IdP details. The following list describes the provider detail keys for each IdP type. For Google and Login with Amazon: client_id client_secret authorize_scopes For Facebook: client_id client_secret authorize_scopes api_version For Sign in with Apple: client_id team_id key_id private_key You can submit a private_key when you add or update an IdP. Describe operations don't return the private key. authorize_scopes For OIDC providers: client_id client_secret attributes_request_method oidc_issuer authorize_scopes The following keys are only present if Amazon Cognito didn't discover them at the authorize_url token_url attributes_url jwks_uri Amazon Cognito sets the value of the following keys automatically. They are read-only. attributes_url_add_attributes For SAML providers: MetadataFile or MetadataURL IDPSignout optional A mapping of IdP attributes to standard and custom user pool attributes. A list of IdP identifiers. The date the IdP was last modified. The date the IdP was created. A container for information about an IdP. The authentication flow for this call to run. The API action will depend on this value. For example: Valid values include: The authentication parameters. These are inputs corresponding to the For For For A map of custom key-value pairs that you can provide as input for certain custom workflows that this action triggers. You create custom workflows by assigning Lambda functions to user pool triggers. When you use the InitiateAuth API action, Amazon Cognito invokes the Lambda functions that are specified for various triggers. The ClientMetadata value is passed as input to the functions for only the following triggers: Pre signup Pre authentication User migration When Amazon Cognito invokes the functions for these triggers, it passes a JSON payload, which the function receives as input. This payload contains a When you use the InitiateAuth API action, Amazon Cognito also invokes the functions for the following triggers, but it doesn't provide the ClientMetadata value as input: Post authentication Custom message Pre token generation Create auth challenge Define auth challenge Verify auth challenge For more information, see Customizing user pool Workflows with Lambda Triggers in the Amazon Cognito Developer Guide. When you use the ClientMetadata parameter, remember that Amazon Cognito won't do the following: Store the ClientMetadata value. This data is available only to Lambda triggers that are assigned to a user pool to support custom workflows. If your user pool configuration doesn't include triggers, the ClientMetadata parameter serves no purpose. Validate the ClientMetadata value. Encrypt the ClientMetadata value. Don't use Amazon Cognito to provide sensitive information. The app client ID. The Amazon Pinpoint analytics metadata that contributes to your metrics for Contextual data about your user session, such as the device fingerprint, IP address, or location. Amazon Cognito advanced security evaluates the risk of an authentication event based on the context that your app generates and passes to Amazon Cognito when it makes API requests. Initiates the authentication request. The name of the challenge that you're responding to with this call. This name is returned in the Valid values include the following: All of the following challenges require Respond to this challenge with In a To set up software token MFA, use the session returned here from The session that should pass both ways in challenge-response calls to the service. If the caller must pass another challenge, they return a session with other challenge parameters. This session should be passed as it is to the next The challenge parameters. These are returned in the All challenges require The result of the authentication response. This result is only returned if the caller doesn't need to pass another challenge. If the caller does need to pass another challenge before it gets tokens, Initiates the authentication response. The message returned when Amazon Cognito throws an internal error exception. This exception is thrown when Amazon Cognito encounters an internal error. The message returned when you have an unverified email address or the identity policy isn't set on an email address that Amazon Cognito can access. This exception is thrown when Amazon Cognito isn't allowed to use your email identity. HTTP status code: 400. The message returned when Amazon Cognito throws an invalid Lambda response exception. This exception is thrown when Amazon Cognito encounters an invalid Lambda response. This exception is thrown when the specified OAuth flow is not valid. The message returned when the Amazon Cognito service throws an invalid parameter exception. This exception is thrown when the Amazon Cognito service encounters an invalid parameter. The message returned when Amazon Cognito throws an invalid user password exception. This exception is thrown when Amazon Cognito encounters an invalid password. The message returned when the invalid SMS role access policy exception is thrown. This exception is returned when the role provided for SMS configuration doesn't have permission to publish using Amazon SNS. The message returned when the role trust relationship for the SMS message is not valid. This exception is thrown when the trust relationship is not valid for the role provided for SMS configuration. This can happen if you don't trust The message returned when the user pool configuration is not valid. This exception is thrown when the user pool configuration is not valid. A pre-registration Lambda trigger. A custom Message Lambda trigger. A post-confirmation Lambda trigger. A pre-authentication Lambda trigger. A post-authentication Lambda trigger. Defines the authentication challenge. Creates an authentication challenge. Verifies the authentication challenge response. A Lambda trigger that is invoked before token generation. The user migration Lambda config type. A custom SMS sender Lambda trigger. A custom email sender Lambda trigger. The Amazon Resource Name (ARN) of an KMS key. Amazon Cognito uses the key to encrypt codes and temporary passwords sent to Specifies the configuration for Lambda triggers. The message returned when Amazon Cognito throws a limit exceeded exception. This exception is thrown when a user exceeds the limit for a requested Amazon Web Services resource. A valid access token that Amazon Cognito issued to the user whose list of devices you want to view. The limit of the device request. The pagination token for the list request. Represents the request to list the devices. The devices returned in the list devices response. The pagination token for the list device response. Represents the response to list devices. The user pool ID for the user pool. The limit of the request to list groups. An identifier that was returned from the previous call to this operation, which can be used to return the next set of items in the list. The group objects for the groups. An identifier that was returned from the previous call to this operation, which can be used to return the next set of items in the list. The user pool ID. The maximum number of IdPs to return. A pagination token. A list of IdP objects. A pagination token. The user pool ID for the user pool. The maximum number of resource servers to return. A pagination token. The resource servers. A pagination token. The Amazon Resource Name (ARN) of the user pool that the tags are assigned to. The tags that are assigned to the user pool. The user pool ID for the user pool that the users are being imported into. The maximum number of import jobs you want the request to return. An identifier that was returned from the previous call to Represents the request to list the user import jobs. The user import jobs. An identifier that can be used to return the next set of user import jobs in the list. Represents the response from the server to the request to list the user import jobs. The user pool ID for the user pool where you want to list user pool clients. The maximum number of results you want the request to return when listing the user pool clients. An identifier that was returned from the previous call to this operation, which can be used to return the next set of items in the list. Represents the request to list the user pool clients. The user pool clients in the response that lists user pool clients. An identifier that was returned from the previous call to this operation, which can be used to return the next set of items in the list. Represents the response from the server that lists user pool clients. An identifier that was returned from the previous call to this operation, which can be used to return the next set of items in the list. The maximum number of results you want the request to return when listing the user pools. Represents the request to list user pools. The user pools from the response to list users. An identifier that was returned from the previous call to this operation, which can be used to return the next set of items in the list. Represents the response to list user pools. The user pool ID for the user pool. The name of the group. The limit of the request to list users. An identifier that was returned from the previous call to this operation, which can be used to return the next set of items in the list. The users returned in the request to list users. An identifier that you can use in a later request to return the next set of items in the list. The user pool ID for the user pool on which the search should be performed. An array of strings, where each string is the name of a user attribute to be returned for each user in the search results. If the array is null, all attributes are returned. Maximum number of users to be returned. An identifier that was returned from the previous call to this operation, which can be used to return the next set of items in the list. A filter string of the form \\\"AttributeName Filter-Type \\\"AttributeValue\\\"\\\". Quotation marks within the filter string must be escaped using the backslash (\\\\) character. For example, \\\" AttributeName: The name of the attribute to search for. You can only search for one attribute at a time. Filter-Type: For an exact match, use =, for example, \\\" AttributeValue: The attribute value that must be matched for each user. If the filter string is empty, You can only search for the following standard attributes: Custom attributes aren't searchable. You can also list users with a client-side filter. The server-side filter matches no more than one attribute. For an advanced search, use a client-side filter with the For more information about server-side and client-side filtering, see FilteringCLI output in the Command Line Interface User Guide. For more information, see Searching for Users Using the ListUsers API and Examples of Using the ListUsers API in the Amazon Cognito Developer Guide. Represents the request to list users. The users returned in the request to list users. An identifier that was returned from the previous call to this operation, which can be used to return the next set of items in the list. The response from the request to list users. The message returned when Amazon Cognito throws an MFA method not found exception. This exception is thrown when Amazon Cognito can't find a multi-factor authentication (MFA) method. The delivery medium to send the MFA code. You can use this parameter to set only the The attribute name of the MFA option type. The only valid value is This data type is no longer supported. Applies only to SMS multi-factor authentication (MFA) configurations. Does not apply to time-based one-time password (TOTP) software token MFA configurations. The message template for SMS messages. The message template for email messages. EmailMessage is allowed only if EmailSendingAccount is DEVELOPER. The subject line for email messages. EmailSubject is allowed only if EmailSendingAccount is DEVELOPER. The message template structure. The device key. The device group key. The new device metadata type. The message returned when the Amazon Cognito service returns a not authorized exception. This exception is thrown when a user isn't authorized. The email address that is sending the email. The address must be either individually verified with Amazon Simple Email Service, or from a domain that has been verified with Amazon SES. The destination to which the receiver of an email should reply to. The Amazon Resource Name (ARN) of the identity that is associated with the sending authorization policy. This identity permits Amazon Cognito to send for the email address specified in the Email template used when a detected risk event is blocked. The email template used when a detected risk event is allowed. The multi-factor authentication (MFA) email template used when MFA is challenged as part of a detected risk. The notify configuration type. The email subject. The email HTML body. The email text body. The notify email type. The minimum value of an attribute that is of the number data type. The maximum value of an attribute that is of the number data type. The minimum and maximum values of an attribute that is of the number data type. The minimum length of the password in the policy that you have set. This value can't be less than 6. In the password policy that you have set, refers to whether you have required users to use at least one uppercase letter in their password. In the password policy that you have set, refers to whether you have required users to use at least one lowercase letter in their password. In the password policy that you have set, refers to whether you have required users to use at least one number in their password. In the password policy that you have set, refers to whether you have required users to use at least one symbol in their password. The number of days a temporary password is valid in the password policy. If the user doesn't sign in during this time, an administrator must reset their password. When you set The password policy type. The message returned when a password reset is required. This exception is thrown when a password reset is required. The message returned when a precondition is not met. This exception is thrown when a precondition is not met. The IdP name. The IdP type. The date the provider was last modified. The date the provider was added to the user pool. A container for IdP details. The name of the provider, such as Facebook, Google, or Login with Amazon. The name of the provider attribute to link to, such as The value of the provider attribute to link to, such as A container for information about an IdP for a user pool. A positive integer specifying priority of a method with 1 being the highest priority. The recovery method for a user. A map containing a priority as a key, and recovery method name as a value. The ID of the client associated with the user pool. A keyed-hash message authentication code (HMAC) calculated using the secret key of a user pool client and username plus the client ID in the message. Contextual data about your user session, such as the device fingerprint, IP address, or location. Amazon Cognito advanced security evaluates the risk of an authentication event based on the context that your app generates and passes to Amazon Cognito when it makes API requests. The The Amazon Pinpoint analytics metadata that contributes to your metrics for A map of custom key-value pairs that you can provide as input for any custom workflows that this action triggers. You create custom workflows by assigning Lambda functions to user pool triggers. When you use the ResendConfirmationCode API action, Amazon Cognito invokes the function that is assigned to the custom message trigger. When Amazon Cognito invokes this function, it passes a JSON payload, which the function receives as input. This payload contains a For more information, see Customizing user pool Workflows with Lambda Triggers in the Amazon Cognito Developer Guide. When you use the ClientMetadata parameter, remember that Amazon Cognito won't do the following: Store the ClientMetadata value. This data is available only to Lambda triggers that are assigned to a user pool to support custom workflows. If your user pool configuration doesn't include triggers, the ClientMetadata parameter serves no purpose. Validate the ClientMetadata value. Encrypt the ClientMetadata value. Don't use Amazon Cognito to provide sensitive information. Represents the request to resend the confirmation code. The code delivery details returned by the server in response to the request to resend the confirmation code. The response from the server when Amazon Cognito makes the request to resend a confirmation code. The message returned when the Amazon Cognito service returns a resource not found exception. This exception is thrown when the Amazon Cognito service can't find the requested resource. The name of the scope. A description of the scope. A resource server scope. The user pool ID for the user pool that hosts the resource server. The identifier for the resource server. The name of the resource server. A list of scopes that are defined for the resource server. A container for information about a resource server for a user pool. The app client ID. The challenge name. For more information, see InitiateAuth. The session that should be passed both ways in challenge-response calls to the service. If The challenge responses. These are inputs corresponding to the value of In a The Amazon Pinpoint analytics metadata that contributes to your metrics for Contextual data about your user session, such as the device fingerprint, IP address, or location. Amazon Cognito advanced security evaluates the risk of an authentication event based on the context that your app generates and passes to Amazon Cognito when it makes API requests. A map of custom key-value pairs that you can provide as input for any custom workflows that this action triggers. You create custom workflows by assigning Lambda functions to user pool triggers. When you use the RespondToAuthChallenge API action, Amazon Cognito invokes any functions that are assigned to the following triggers: post authentication, pre token generation, define auth challenge, create auth challenge, and verify auth challenge. When Amazon Cognito invokes any of these functions, it passes a JSON payload, which the function receives as input. This payload contains a For more information, see Customizing user pool Workflows with Lambda Triggers in the Amazon Cognito Developer Guide. When you use the ClientMetadata parameter, remember that Amazon Cognito won't do the following: Store the ClientMetadata value. This data is available only to Lambda triggers that are assigned to a user pool to support custom workflows. If your user pool configuration doesn't include triggers, the ClientMetadata parameter serves no purpose. Validate the ClientMetadata value. Encrypt the ClientMetadata value. Don't use Amazon Cognito to provide sensitive information. The request to respond to an authentication challenge. The challenge name. For more information, see InitiateAuth. The session that should be passed both ways in challenge-response calls to the service. If the caller must pass another challenge, they return a session with other challenge parameters. This session should be passed as it is to the next The challenge parameters. For more information, see InitiateAuth. The result returned by the server in response to the request to respond to the authentication challenge. The response to respond to the authentication challenge. The refresh token that you want to revoke. The client ID for the token that you want to revoke. The secret for the client ID. This is required only if the client ID has a secret. The user pool ID. The app client ID. The compromised credentials risk configuration object, including the The account takeover risk configuration object, including the The configuration to override the risk decision. The last modified date. The risk configuration type. Overrides the risk decision to always block the pre-authentication requests. The IP range is in CIDR notation, a compact representation of an IP address and its routing prefix. Risk detection isn't performed on the IP addresses in this range list. The IP range is in CIDR notation. The type of the configuration to override the risk decision.MessageAction
isn't set, the default is to send a welcome message via email or phone (SMS).AdminCreateUser
with SUPPRESS
for the MessageAction
parameter, and Amazon Cognito won't send any email. FORCE_CHANGE_PASSWORD
state until they sign in and change their password.AdminCreateUser
requires developer credentials.DestinationUser
, the user must create a new user account. See AdminLinkProviderForUser.ProviderName
must match the value specified when creating an IdP for the pool. ProviderName
value must be Cognito
and the ProviderAttributeName
must be Cognito_Subject
. The ProviderAttributeValue
must be the name that is used in the user pool for the user.ProviderAttributeName
must always be Cognito_Subject
for social IdPs. The ProviderAttributeValue
must always be the exact subject that was used when the user was originally linked as a source user.ProviderAttributeName
and ProviderAttributeValue
must be the same values that were used for the SourceUser
when the identities were originally linked using AdminLinkProviderForUser
call. (If the linking was done with ProviderAttributeName
set to Cognito_Subject
, the same applies here). However, if the user has already signed in, the ProviderAttributeName
must be Cognito_Subject
and ProviderAttributeValue
must be the subject of the SAML assertion.GetUser
and ListUsers
API requests.cognito-idp:AdminDisableUser
permissions.DestinationUser
) to an identity from an external IdP (SourceUser
) based on a specified attribute name and value from the external IdP. This allows you to create a link from the existing user account to an external federated user identity that has not yet been used to sign in. You can then use the federated user identity to sign in as the existing user account. FORCE_CHANGE_PASSWORD
state. When the user next tries to sign in, the InitiateAuth/AdminInitiateAuth response will contain the NEW_PASSWORD_REQUIRED
challenge. If the user doesn't sign in before it expires, the user won't be able to sign in, and an administrator must reset their password. Confirmed
.custom:
prefix to the attribute name.AdminUserGlobalSignOut
requests with Amazon Web Services credentials. It also invalidates all refresh tokens that Amazon Cognito has issued to a user. The user's current access and ID tokens remain valid until they expire. By default, access and ID tokens expire one hour after they're issued. A user can still use a hosted UI cookie to retrieve new tokens for the duration of the cookie validity period of 1 hour.AssociateSoftwareToken
request with either the user's access token, or a session string from a challenge response that you received from Amazon Cognito.MFA_SETUP
or SOFTWARE_TOKEN_SETUP
challenge each time your user signs. Complete setup with AssociateSoftwareToken
and VerifySoftwareToken
.SOFTWARE_TOKEN_MFA
challenge when they authenticate. Respond to this challenge with your user's TOTP.Username
parameter, you can use the username or user alias. The method used to send the confirmation code is sent according to the specified AccountRecoverySetting. For more information, see Recovering User Accounts in the Amazon Cognito Developer Guide. If neither a verified phone number nor a verified email exists, an InvalidParameterException
is thrown. To use the confirmation code for resetting the password, call ConfirmForgotPassword. GetSigningCertificate
, but doesn't invalidate the original certificate.clientId
is ALL
), then that information is returned. If nothing is present, then an empty shape is returned.InitiateAuth
. For more information, see Adding user pool sign-in through a third party.UserPoolId
or ClientId
, pass null values for all four configuration types.UserPoolAddOns
keyAdvancedSecurityMode
.clientId
) or for all clients (by setting the clientId
to ALL
). If you specify ALL
, the default configuration is used for every client that has no previously set UI customization. If you specify UI customization settings for a particular client, it will no longer return to the ALL
configuration.Environment
tag key to both user pools. The value of this key might be Test
for one user pool, and Production
for the other.RecoveryOptionTypes
.AccountRecoverySetting
.
\"\
}\
},\
\"documentation\":\"BLOCK
Choosing this action will block the request.MFA_IF_CONFIGURED
Present an MFA challenge if user has configured it, else allow the request.MFA_REQUIRED
Present an MFA challenge if user has configured it, else block the request.NO_ACTION
Allow the user to sign in.clientMetadata
attribute provides the data that you assigned to the ClientMetadata parameter in your AdminConfirmSignUp request. In your function code in Lambda, you can process the ClientMetadata value to enhance your workflow for your specific needs.
True
if only the administrator is allowed to create user profiles. Set to False
if users can sign themselves up via an app.AdminCreateUser
again, specifying \\\"RESEND\\\"
for the MessageAction
parameter. The default value for this parameter is 7. TemporaryPasswordValidityDays
in PasswordPolicy
, that value will be used, and UnusedAccountValidityDays
will be no longer be an available parameter for that user pool.Username
. However, any attributes that you specify as required (when creating a user pool or in the Attributes tab of the console) either you should supply (in your call to AdminCreateUser
) or the user should supply (when they sign up in response to your welcome message).custom:
prefix to the attribute name.AdminCreateUser
, you can set the email_verified
attribute to True
, and you can set the phone_number_verified
attribute to True
. You can also do this by calling AdminUpdateUserAttributes.
\"\
},\
\"ValidationData\":{\
\"shape\":\"AttributeListType\",\
\"documentation\":\"email_verified
attribute is set to True
, or if \\\"EMAIL\\\"
is specified in the DesiredDeliveryMediums
parameter.phone_number_verified
attribute is set to True
, or if \\\"SMS\\\"
is specified in the DesiredDeliveryMediums
parameter.AdminCreateUser
again, specifying \\\"RESEND\\\"
for the MessageAction
parameter.phone_number_verified
or email_verified
attribute is set to True
. Otherwise, it is ignored.True
and the phone number or email address specified in the UserAttributes parameter already exists as an alias with a different user, the API call will migrate the alias from the previous user to the newly created user. The previous user will no longer be able to log in using that alias.False
, the API throws an AliasExistsException
error if the alias already exists. The default value is False
.RESEND
to resend the invitation message to a user that already exists and reset the expiration limit on the user's account. Set to SUPPRESS
to suppress sending the message. You can specify only one value.\\\"EMAIL\\\"
if email will be used to send the welcome message. Specify \\\"SMS\\\"
if the phone number will be used. The default value is \\\"SMS\\\"
. You can specify more than one value.clientMetadata
attribute, which provides the data that you assigned to the ClientMetadata parameter in your AdminCreateUser request. In your function code in Lambda, you can process the clientMetadata
value to enhance your workflow for your specific needs.
custom:
prefix to the attribute name.enabled
.
\"\
},\
\"MFAOptions\":{\
\"shape\":\"MFAOptionListType\",\
\"documentation\":\"SMS_MFA
and SOFTWARE_TOKEN_MFA
.
REFRESH_TOKEN_AUTH
will take in a valid refresh token and return new tokens.USER_SRP_AUTH
will take in USERNAME
and SRP_A
and return the Secure Remote Password (SRP) protocol variables to be used for next challenge execution.ADMIN_USER_PASSWORD_AUTH
will take in USERNAME
and PASSWORD
and return the next challenge or tokens.
\"\
},\
\"AuthParameters\":{\
\"shape\":\"AuthParametersType\",\
\"documentation\":\"USER_SRP_AUTH
: Authentication flow for the Secure Remote Password (SRP) protocol.REFRESH_TOKEN_AUTH
/REFRESH_TOKEN
: Authentication flow for refreshing the access token and ID token by supplying a valid refresh token.CUSTOM_AUTH
: Custom authentication flow.ADMIN_NO_SRP_AUTH
: Non-SRP authentication flow; you can pass in the USERNAME and PASSWORD directly if the flow is enabled for calling the app client.ADMIN_USER_PASSWORD_AUTH
: Admin-based user password authentication. This replaces the ADMIN_NO_SRP_AUTH
authentication flow. In this flow, Amazon Cognito receives the password in the request instead of using the SRP process to verify passwords.AuthFlow
that you're invoking. The required values depend on the value of AuthFlow
:
\"\
},\
\"ClientMetadata\":{\
\"shape\":\"ClientMetadataType\",\
\"documentation\":\"USER_SRP_AUTH
: USERNAME
(required), SRP_A
(required), SECRET_HASH
(required if the app client is configured with a client secret), DEVICE_KEY
.REFRESH_TOKEN_AUTH/REFRESH_TOKEN
: REFRESH_TOKEN
(required), SECRET_HASH
(required if the app client is configured with a client secret), DEVICE_KEY
.ADMIN_NO_SRP_AUTH
: USERNAME
(required), SECRET_HASH
(if app client is configured with client secret), PASSWORD
(required), DEVICE_KEY
.CUSTOM_AUTH
: USERNAME
(required), SECRET_HASH
(if app client is configured with client secret), DEVICE_KEY
. To start the authentication flow with password verification, include ChallengeName: SRP_A
and SRP_A: (The SRP_A Value)
.
validationData
attribute, which provides the data that you assigned to the ClientMetadata parameter in your AdminInitiateAuth request. In your function code in Lambda, you can process the validationData
value to enhance your workflow for your specific needs.
AdminInitiateAuth
calls.AdminInitiateAuth
response if you must pass another challenge.
\"\
},\
\"Session\":{\
\"shape\":\"SessionType\",\
\"documentation\":\"MFA_SETUP
: If MFA is required, users who don't have at least one of the MFA methods set up are presented with an MFA_SETUP
challenge. The user must set up at least one MFA type to continue to authenticate.SELECT_MFA_TYPE
: Selects the MFA type. Valid MFA options are SMS_MFA
for text SMS MFA, and SOFTWARE_TOKEN_MFA
for time-based one-time password (TOTP) software token MFA.SMS_MFA
: Next challenge is to supply an SMS_MFA_CODE
, delivered via SMS.PASSWORD_VERIFIER
: Next challenge is to supply PASSWORD_CLAIM_SIGNATURE
, PASSWORD_CLAIM_SECRET_BLOCK
, and TIMESTAMP
after the client-side SRP calculations.CUSTOM_CHALLENGE
: This is returned if your custom authentication flow determines that the user should pass another challenge before tokens are issued.DEVICE_SRP_AUTH
: If device tracking was activated in your user pool and the previous challenges were passed, this challenge is returned so that Amazon Cognito can start tracking this device.DEVICE_PASSWORD_VERIFIER
: Similar to PASSWORD_VERIFIER
, but for devices only.ADMIN_NO_SRP_AUTH
: This is returned if you must authenticate with USERNAME
and PASSWORD
directly. An app client must be enabled to use this flow.NEW_PASSWORD_REQUIRED
: For users who are required to change their passwords after successful first login. Respond to this challenge with NEW_PASSWORD
and any required attributes that Amazon Cognito returned in the requiredAttributes
parameter. You can also set values for attributes that aren't required by your user pool and that your app client can write. For more information, see AdminRespondToAuthChallenge.NEW_PASSWORD_REQUIRED
challenge response, you can't modify a required attribute that already has a value. In AdminRespondToAuthChallenge
, set a value for any keys that Amazon Cognito returned in the requiredAttributes
parameter, then use the AdminUpdateUserAttributes
API operation to modify the value of any additional attributes.MFA_SETUP
: For users who are required to set up an MFA factor before they can sign in. The MFA types activated for the user pool will be listed in the challenge parameters MFA_CAN_SETUP
value. InitiateAuth
as an input to AssociateSoftwareToken
, and use the session returned by VerifySoftwareToken
as an input to RespondToAuthChallenge
with challenge name MFA_SETUP
to complete sign-in. To set up SMS MFA, users will need help from an administrator to add a phone number to their account and then call InitiateAuth
again to restart sign-in.AdminInitiateAuth
or AdminRespondToAuthChallenge
API call determines that the caller must pass another challenge, they return a session with other challenge parameters. This session should be passed as it is to the next AdminRespondToAuthChallenge
API call.AdminInitiateAuth
response if you must pass another challenge. The responses in this parameter should be used to compute inputs to the next call (AdminRespondToAuthChallenge
).USERNAME
and SECRET_HASH
(if applicable).USER_ID_FOR_SRP
attribute is the user's actual username, not an alias (such as email address or phone number), even if you specified an alias in your call to AdminInitiateAuth
. This happens because, in the AdminRespondToAuthChallenge
API ChallengeResponses
, the USERNAME
attribute can't be an alias.ChallengeName
, ChallengeParameters
, and Session
are returned.ProviderAttributeValue
for the DestinationUser
should be the username in the user pool. For a federated user, it should be the provider-specific user_id
.ProviderAttributeName
of the DestinationUser
is ignored.ProviderName
should be set to Cognito
for users in Cognito user pools.SourceUser
is using a federated social IdP, such as Facebook, Google, or Login with Amazon, you must set the ProviderAttributeName
to Cognito_Subject
. For social IdPs, the ProviderName
will be Facebook
, Google
, or LoginWithAmazon
, and Amazon Cognito will automatically parse the Facebook, Google, and Login with Amazon tokens for id
, sub
, and user_id
, respectively. The ProviderAttributeValue
for the user must be the same value as the id
, sub
, or user_id
value found in the social IdP token.ProviderAttributeName
can be any value that matches a claim in the SAML assertion. If you want to link SAML users based on the subject of the SAML assertion, you should map the subject to a claim through the SAML IdP and submit that claim name as the ProviderAttributeName
. If you set ProviderAttributeName
to Cognito_Subject
, Amazon Cognito will automatically parse the default unique identifier found in the subject from the SAML token.MaxResults
to 0, or if you don't include a MaxResults
parameter.EventID
, EventType
, CreationDate
, EventRisk
, and EventResponse
.clientMetadata
attribute, which provides the data that you assigned to the ClientMetadata parameter in your AdminResetUserPassword request. In your function code in Lambda, you can process the clientMetadata
value to enhance your workflow for your specific needs.
ChallengeName
, for example:
SMS_MFA
: SMS_MFA_CODE
, USERNAME
, SECRET_HASH
(if app client is configured with client secret).PASSWORD_VERIFIER
: PASSWORD_CLAIM_SIGNATURE
, PASSWORD_CLAIM_SECRET_BLOCK
, TIMESTAMP
, USERNAME
, SECRET_HASH
(if app client is configured with client secret).PASSWORD_VERIFIER
requires DEVICE_KEY
when signing in with a remembered device.ADMIN_NO_SRP_AUTH
: PASSWORD
, USERNAME
, SECRET_HASH
(if app client is configured with client secret). NEW_PASSWORD_REQUIRED
: NEW_PASSWORD
, USERNAME
, SECRET_HASH
(if app client is configured with client secret). To set any required attributes that Amazon Cognito returned as requiredAttributes
in the AdminInitiateAuth
response, add a userAttributes.attributename
parameter. This parameter can also set values for writable attributes that aren't required by your user pool.NEW_PASSWORD_REQUIRED
challenge response, you can't modify a required attribute that already has a value. In AdminRespondToAuthChallenge
, set a value for any keys that Amazon Cognito returned in the requiredAttributes
parameter, then use the AdminUpdateUserAttributes
API operation to modify the value of any additional attributes.MFA_SETUP
requires USERNAME
, plus you must use the session value returned by VerifySoftwareToken
in the Session
parameter.USERNAME
attribute must be the user's actual username, not an alias (such as an email address or phone number). To make this simpler, the AdminInitiateAuth
response includes the actual username value in the USERNAMEUSER_ID_FOR_SRP
attribute. This happens even if you specified an alias in your call to AdminInitiateAuth
.InitiateAuth
or RespondToAuthChallenge
API call determines that the caller must pass another challenge, it returns a session with other challenge parameters. This session should be passed as it is to the next RespondToAuthChallenge
API call.AdminRespondToAuthChallenge
calls.
clientMetadata
attribute that provides the data that you assigned to the ClientMetadata parameter in your AdminRespondToAuthChallenge request. In your function code in Lambda, you can process the clientMetadata
value to enhance your workflow for your specific needs.
RespondToAuthChallenge
API call.True
if the password is permanent, False
if it is temporary.custom:
prefix to the attribute name.email_verified
or phone_number_verified
attribute, with a value of true
. If you set the email_verified
or phone_number_verified
value for an email
or phone_number
attribute that requires verification to true
, Amazon Cognito doesnât send a verification message to your user.clientMetadata
attribute, which provides the data that you assigned to the ClientMetadata parameter in your AdminUpdateUserAttributes request. In your function code in Lambda, you can process the clientMetadata
value to enhance your workflow for your specific needs.
UserDataShared
is true
, Amazon Cognito includes user data in the events that it publishes to Amazon Pinpoint analytics.ConfirmForgotPassword
calls.clientMetadata
attribute, which provides the data that you assigned to the ClientMetadata parameter in your ConfirmForgotPassword request. In your function code in Lambda, you can process the clientMetadata
value to enhance your workflow for your specific needs.
False
. If this parameter is set to True
and the phone number/email used for sign up confirmation already exists as an alias with a different user, the API call will migrate the alias from the previous user to the newly created user being confirmed. If set to False
, the API will throw an AliasExistsException error.ConfirmSignUp
calls.clientMetadata
attribute, which provides the data that you assigned to the ClientMetadata parameter in your ConfirmSignUp request. In your function code in Lambda, you can process the clientMetadata
value to enhance your workflow for your specific needs.
Precedence
values take precedence over groups with higher or null Precedence
values. If a user belongs to two or more groups, it is the group with the lowest precedence value whose role ARN is given in the user's tokens for the cognito:roles
and cognito:preferred_role
claims.Precedence
value. If this happens, neither group takes precedence over the other. If two groups with the same Precedence
have the same role ARN, that role is used in the cognito:preferred_role
claim in tokens for users in each group. If the two groups have different role ARNs, the cognito:preferred_role
claim isn't set in users' tokens.Precedence
value is null. The maximum Precedence
value is 2^31-1
.
\"\
},\
\"AttributeMapping\":{\
\"shape\":\"AttributeMappingType\",\
\"documentation\":\"
oidc_issuer
URL.
https://my-weather-api.example.com
.name
and description
.RefreshTokenValidity
as seconds
, minutes
, hours
, or days
, set a TokenValidityUnits
value in your API request.RefreshTokenValidity
as 10
and TokenValidityUnits
as days
, your user can refresh their session and retrieve new access and ID tokens for 10 days.RefreshTokenValidity
in an API request is days. You can't set RefreshTokenValidity
to 0. If you do, Amazon Cognito overrides the value with the default value of 30 days. Valid range is displayed below in seconds.AccessTokenValidity
as seconds
, minutes
, hours
, or days
, set a TokenValidityUnits
value in your API request.AccessTokenValidity
to 10
and TokenValidityUnits
to hours
, your user can authorize access with their access token for 10 hours.AccessTokenValidity
in an API request is hours. Valid range is displayed below in seconds.IdTokenValidity
as seconds
, minutes
, hours
, or days
, set a TokenValidityUnits
value in your API request.IdTokenValidity
as 10
and TokenValidityUnits
as hours
, your user can authenticate their session with their ID token for 10 hours.AccessTokenValidity
in an API request is hours. Valid range is displayed below in seconds.ExplicitAuthFlows
, your user client supports ALLOW_REFRESH_TOKEN_AUTH
, ALLOW_USER_SRP_AUTH
, and ALLOW_CUSTOM_AUTH
.
ALLOW_ADMIN_USER_PASSWORD_AUTH
: Enable admin based user password authentication flow ADMIN_USER_PASSWORD_AUTH
. This setting replaces the ADMIN_NO_SRP_AUTH
setting. With this authentication flow, your app passes a user name and password to Amazon Cognito in the request, instead of using the Secure Remote Password (SRP) protocol to securely transmit the password.ALLOW_CUSTOM_AUTH
: Enable Lambda trigger based authentication.ALLOW_USER_PASSWORD_AUTH
: Enable user password-based authentication. In this flow, Amazon Cognito receives the password in the request instead of using the SRP protocol to verify passwords.ALLOW_USER_SRP_AUTH
: Enable SRP-based authentication.ALLOW_REFRESH_TOKEN_AUTH
: Enable authflow to refresh tokens.ADMIN_NO_SRP_AUTH
, CUSTOM_AUTH_FLOW_ONLY
, or USER_PASSWORD_AUTH
. You can't assign these legacy ExplicitAuthFlows
values to user pool clients at the same time as values that begin with ALLOW_
, like ALLOW_USER_SRP_AUTH
.COGNITO
, Facebook
, Google
, SignInWithApple
, and LoginWithAmazon
. You can also specify the names that you configured for the SAML and OIDC IdPs in your user pool, for example MySAMLIdP
or MyOIDCIdP
.
CallbackURLs
list.
\"\
},\
\"AllowedOAuthScopes\":{\
\"shape\":\"ScopeListType\",\
\"documentation\":\"/oauth2/token
endpoint./oauth2/token
endpoint directly to a non-person user using a combination of the client ID and client secret.phone
, email
, openid
, and profile
. Possible values provided by Amazon Web Services are aws.cognito.signin.user.admin
. Custom scopes created in Resource Servers are also supported.ENABLED
and the user doesn't exist, authentication returns an error indicating either the username or password was incorrect. Account confirmation and password recovery return a response indicating a code was sent to a simulated destination. When set to LEGACY
, those APIs return a UserNotFoundException
exception if the user doesn't exist in the user pool.
\"\
},\
\"EnableTokenRevocation\":{\
\"shape\":\"WrappedBooleanType\",\
\"documentation\":\"ENABLED
- This prevents user existence-related errors.LEGACY
- This represents the early behavior of Amazon Cognito where user existence related errors aren't prevented.EnablePropagateAdditionalUserContextData
in an app client that has a client secret.AuthSessionValidity
is the duration, in minutes, of that session token. Your user pool native user must respond to each authentication challenge before the session expires.auth.example.com
. For Amazon Cognito prefix domains, this is the prefix alone, such as auth
.DeletionProtection
prevents accidental deletion of your user pool. Before you can delete a user pool that you have protected against deletion, you must deactivate this feature.DeleteUserPool
API request, Amazon Cognito returns an InvalidParameterException
error. To delete a protected user pool, send a new DeleteUserPool
request after you deactivate deletion protection in an UpdateUserPool
API request.AttributesRequireVerificationBeforeUpdate
, a user-pool setting that tells Amazon Cognito how to handle changes to the value of your users' email address and phone number attributes. For more information, see Verifying updates to email addresses and phone numbers.DeviceConfiguration
field, you activate the Amazon Cognito device-remembering feature.AdminCreateUser
requests.AdvancedSecurityMode
to the value \\\"AUDIT\\\".False
, users can sign in using either \\\"username\\\" or \\\"Username\\\". This configuration is immutable once it has been set. For more information, see UsernameConfigurationType.ForgotPassword
. You can use this setting to define a preferred method when a user has more than one method available. With this setting, SMS doesn't qualify for a valid password recovery mechanism if the user also has SMS multi-factor authentication (MFA) activated. In the absence of this setting, Amazon Cognito uses the legacy behavior to determine the recovery method where SMS is preferred through email.V1_0
.V1_0
.custom:
prefix to the front of the attribute name.auth.example.com
. For Amazon Cognito prefix domains, this is the prefix alone, such as auth
.auth.example.com
. For Amazon Cognito prefix domains, this is the prefix alone, such as auth
.ChallengeRequiredOnNewDevice
is true, users who sign in with devices that have not been confirmed or remembered must still provide a second factor in a user pool that requires MFA.DeviceOnlyRememberedOnUserPrompt
is false
, Amazon Cognito immediately remembers devices that you register in a ConfirmDevice
API request.DeviceOnlyRememberedOnUserPrompt
is true
, you must follow ConfirmDevice
with an UpdateDeviceStatus API request that sets the user's device to remembered
or not_remembered
.DEVICE_KEY
in the authentication parameters in your user's InitiateAuth request. If your app doesn't include a DEVICE_KEY
parameter, the response from Amazon Cognito includes newly-generated DEVICE_KEY
and DEVICE_GROUP_KEY
values under NewDeviceMetadata
. Store these values to use in future device-authentication requests.DeviceConfiguration
, you activate the device remembering for the user pool.auth.example.com
. For Amazon Cognito prefix domains, this is the prefix alone, such as auth
.EmailSendingAccount
parameter:
COGNITO_DEFAULT
, Amazon Cognito uses this address as the custom FROM address when it emails your users using its built-in email account.DEVELOPER
, Amazon Cognito emails your users with this address by calling Amazon SES on your behalf.SourceArn
parameter must indicate a supported Amazon Web Services Region of your user pool. Typically, the Region in the SourceArn
and the user pool Region are the same. For more information, see Amazon SES email configuration regions in the Amazon Cognito Developer Guide.
\"\
},\
\"From\":{\
\"shape\":\"StringType\",\
\"documentation\":\"no-reply@verificationemail.com
. To customize the FROM address, provide the Amazon Resource Name (ARN) of an Amazon SES verified email address for the SourceArn
parameter.SourceArn
parameter.testuser@example.com
or Test User <testuser@example.com>
. This address appears before the body of the email.
\"\
}\
},\
\"documentation\":\"ForgotPassword
calls.clientMetadata
attribute, which provides the data that you assigned to the ClientMetadata parameter in your ForgotPassword request. In your function code in Lambda, you can process the clientMetadata
value to enhance your workflow for your specific needs.
clientMetadata
attribute, which provides the data that you assigned to the ClientMetadata parameter in your GetUserAttributeVerificationCode request. In your function code in Lambda, you can process the clientMetadata
value to enhance your workflow for your specific needs.
\"\
}\
}\
},\
\"GetUserRequest\":{\
\"type\":\"structure\",\
\"required\":[\"AccessToken\"],\
\"members\":{\
\"AccessToken\":{\
\"shape\":\"TokenModelType\",\
\"documentation\":\"OFF
MFA won't be used for any users.ON
MFA is required for all users to sign in.OPTIONAL
MFA will be required only for individual users who have an MFA factor activated.custom:
prefix to the attribute name.SMS_MFA
and SOFTWARE_TOKEN_MFA
.Precedence
values take precedence over groups with higher ornull Precedence
values. If a user belongs to two or more groups, it is the group with the lowest precedence value whose role ARN is given in the user's tokens for the cognito:roles
and cognito:preferred_role
claims.Precedence
value. If this happens, neither group takes precedence over the other. If two groups with the same Precedence
have the same role ARN, that role is used in the cognito:preferred_role
claim in tokens for users in each group. If the two groups have different role ARNs, the cognito:preferred_role
claim isn't set in users' tokens.Precedence
value is null.
\"\
},\
\"AttributeMapping\":{\
\"shape\":\"AttributeMappingType\",\
\"documentation\":\"
oidc_issuer
URL.
REFRESH_TOKEN_AUTH
takes in a valid refresh token and returns new tokens.USER_SRP_AUTH
takes in USERNAME
and SRP_A
and returns the SRP variables to be used for next challenge execution.USER_PASSWORD_AUTH
takes in USERNAME
and PASSWORD
and returns the next challenge or tokens.
USER_SRP_AUTH
: Authentication flow for the Secure Remote Password (SRP) protocol.REFRESH_TOKEN_AUTH
/REFRESH_TOKEN
: Authentication flow for refreshing the access token and ID token by supplying a valid refresh token.CUSTOM_AUTH
: Custom authentication flow.USER_PASSWORD_AUTH
: Non-SRP authentication flow; user name and password are passed directly. If a user migration Lambda trigger is set, this flow will invoke the user migration Lambda if it doesn't find the user name in the user pool. ADMIN_NO_SRP_AUTH
isn't a valid value.AuthFlow
that you're invoking. The required values depend on the value of AuthFlow
:
\"\
},\
\"ClientMetadata\":{\
\"shape\":\"ClientMetadataType\",\
\"documentation\":\"USER_SRP_AUTH
: USERNAME
(required), SRP_A
(required), SECRET_HASH
(required if the app client is configured with a client secret), DEVICE_KEY
.REFRESH_TOKEN_AUTH/REFRESH_TOKEN
: REFRESH_TOKEN
(required), SECRET_HASH
(required if the app client is configured with a client secret), DEVICE_KEY
.CUSTOM_AUTH
: USERNAME
(required), SECRET_HASH
(if app client is configured with client secret), DEVICE_KEY
. To start the authentication flow with password verification, include ChallengeName: SRP_A
and SRP_A: (The SRP_A Value)
.
validationData
attribute, which provides the data that you assigned to the ClientMetadata parameter in your InitiateAuth request. In your function code in Lambda, you can process the validationData
value to enhance your workflow for your specific needs.
InitiateAuth
calls.AdminInitiateAuth
response if you must pass another challenge.USERNAME
and SECRET_HASH
(if applicable) in the parameters.
\"\
},\
\"Session\":{\
\"shape\":\"SessionType\",\
\"documentation\":\"SMS_MFA
: Next challenge is to supply an SMS_MFA_CODE
, delivered via SMS.PASSWORD_VERIFIER
: Next challenge is to supply PASSWORD_CLAIM_SIGNATURE
, PASSWORD_CLAIM_SECRET_BLOCK
, and TIMESTAMP
after the client-side SRP calculations.CUSTOM_CHALLENGE
: This is returned if your custom authentication flow determines that the user should pass another challenge before tokens are issued.DEVICE_SRP_AUTH
: If device tracking was activated on your user pool and the previous challenges were passed, this challenge is returned so that Amazon Cognito can start tracking this device.DEVICE_PASSWORD_VERIFIER
: Similar to PASSWORD_VERIFIER
, but for devices only.NEW_PASSWORD_REQUIRED
: For users who are required to change their passwords after successful first login. NEW_PASSWORD
and any required attributes that Amazon Cognito returned in the requiredAttributes
parameter. You can also set values for attributes that aren't required by your user pool and that your app client can write. For more information, see RespondToAuthChallenge.NEW_PASSWORD_REQUIRED
challenge response, you can't modify a required attribute that already has a value. In RespondToAuthChallenge
, set a value for any keys that Amazon Cognito returned in the requiredAttributes
parameter, then use the UpdateUserAttributes
API operation to modify the value of any additional attributes.MFA_SETUP
: For users who are required to setup an MFA factor before they can sign in. The MFA types activated for the user pool will be listed in the challenge parameters MFA_CAN_SETUP
value. InitiateAuth
as an input to AssociateSoftwareToken
. Use the session returned by VerifySoftwareToken
as an input to RespondToAuthChallenge
with challenge name MFA_SETUP
to complete sign-in. To set up SMS MFA, an administrator should help the user to add a phone number to their account, and then the user should call InitiateAuth
again to restart sign-in.RespondToAuthChallenge
API call.InitiateAuth
response if you must pass another challenge. The responses in this parameter should be used to compute inputs to the next call (RespondToAuthChallenge
). USERNAME
and SECRET_HASH
(if applicable).ChallengeName
, ChallengeParameters
, and Session
are returned.cognito-idp.amazonaws.com
or the external ID provided in the role does not match what is provided in the SMS configuration for the user pool.CustomEmailSender
and CustomSMSSender
.ListUserImportJobs
, which can be used to return the next set of import jobs in the list.family_name
= \\\\\\\"Reddy\\\\\\\"\\\".
given_name
= \\\\\\\"Jon\\\\\\\"\\\". For a prefix (\\\"starts with\\\") match, use ^=, for example, \\\"given_name
^= \\\\\\\"Jon\\\\\\\"\\\". ListUsers
returns all users in the user pool.
username
(case-sensitive)email
phone_number
name
given_name
family_name
preferred_username
cognito:user_status
(called Status in the Console) (case-insensitive)status (called Enabled in the Console) (case-sensitive)
sub
--query
parameter of the list-users
action in the CLI. When you use a client-side filter, ListUsers returns a paginated list of zero or more users. You can receive multiple pages in a row with zero results. Repeat the query with each pagination token that is returned until you receive a null pagination token value, and then review the combined result. SMS
delivery medium value.phone_number
.From
parameter.TemporaryPasswordValidityDays
for a user pool, you can no longer set a value for the legacy UnusedAccountValidityDays
parameter in that user pool.NameID
.xxxxx_account
.username
attribute of the user to whom you want to resend a confirmation code.ResendConfirmationCode
calls.clientMetadata
attribute, which provides the data that you assigned to the ClientMetadata parameter in your ResendConfirmationCode request. In your function code in Lambda, you can process the clientMetadata
value to enhance your workflow for your specific needs.
ADMIN_NO_SRP_AUTH
isn't a valid value.InitiateAuth
or RespondToAuthChallenge
API call determines that the caller must pass another challenge, they return a session with other challenge parameters. This session should be passed as it is to the next RespondToAuthChallenge
API call.ChallengeName
, for example:SECRET_HASH
(if app client is configured with client secret) applies to all of the inputs that follow (including SOFTWARE_TOKEN_MFA
).
\"\
},\
\"AnalyticsMetadata\":{\
\"shape\":\"AnalyticsMetadataType\",\
\"documentation\":\"SMS_MFA
: SMS_MFA_CODE
, USERNAME
.PASSWORD_VERIFIER
: PASSWORD_CLAIM_SIGNATURE
, PASSWORD_CLAIM_SECRET_BLOCK
, TIMESTAMP
, USERNAME
.PASSWORD_VERIFIER
requires DEVICE_KEY
when you sign in with a remembered device.NEW_PASSWORD_REQUIRED
: NEW_PASSWORD
, USERNAME
, SECRET_HASH
(if app client is configured with client secret). To set any required attributes that Amazon Cognito returned as requiredAttributes
in the InitiateAuth
response, add a userAttributes.attributename
parameter. This parameter can also set values for writable attributes that aren't required by your user pool.NEW_PASSWORD_REQUIRED
challenge response, you can't modify a required attribute that already has a value. In RespondToAuthChallenge
, set a value for any keys that Amazon Cognito returned in the requiredAttributes
parameter, then use the UpdateUserAttributes
API operation to modify the value of any additional attributes.SOFTWARE_TOKEN_MFA
: USERNAME
and SOFTWARE_TOKEN_MFA_CODE
are required attributes.DEVICE_SRP_AUTH
requires USERNAME
, DEVICE_KEY
, SRP_A
(and SECRET_HASH
).DEVICE_PASSWORD_VERIFIER
requires everything that PASSWORD_VERIFIER
requires, plus DEVICE_KEY
.MFA_SETUP
requires USERNAME
, plus you must use the session value returned by VerifySoftwareToken
in the Session
parameter.RespondToAuthChallenge
calls.clientMetadata
attribute, which provides the data that you assigned to the ClientMetadata parameter in your RespondToAuthChallenge request. In your function code in Lambda, you can process the clientMetadata
value to enhance your workflow for your specific needs.
RespondToAuthChallenge
API call.EventFilter
and the EventAction
.NotifyConfiguration
object and Actions
to take if there is an account takeover.
Specifies whether SMS is the preferred MFA method.
\"\ }\ },\ \"documentation\":\"The type used for enabling SMS multi-factor authentication (MFA) at the user level. Phone numbers don't need to be verified to be used for SMS MFA. If an MFA type is activated for a user, the user will be prompted for MFA during all sign-in attempts, unless device tracking is turned on and the device has been trusted. If you would like MFA to be applied selectively based on the assessed risk level of sign-in attempts, deactivate MFA for users and turn on Adaptive Authentication for the user pool.
\"\ },\ \"SchemaAttributeType\":{\ \"type\":\"structure\",\ \"members\":{\ \"Name\":{\ \"shape\":\"CustomAttributeNameType\",\ \"documentation\":\"A schema attribute of the name type.
\"\ },\ \"AttributeDataType\":{\ \"shape\":\"AttributeDataType\",\ \"documentation\":\"The attribute data type.
\"\ },\ \"DeveloperOnlyAttribute\":{\ \"shape\":\"BooleanType\",\ \"documentation\":\"You should use WriteAttributes in the user pool client to control how attributes can be mutated for new use cases instead of using DeveloperOnlyAttribute
.
Specifies whether the attribute type is developer only. This attribute can only be modified by an administrator. Users won't be able to modify this attribute using their access token. For example, DeveloperOnlyAttribute
can be modified using AdminUpdateUserAttributes but can't be updated using UpdateUserAttributes.
Specifies whether the value of the attribute can be changed.
For any user pool attribute that is mapped to an IdP attribute, you must set this parameter to true
. Amazon Cognito updates mapped attributes when users sign in to your application through an IdP. If an attribute is immutable, Amazon Cognito throws an error when it attempts to update the attribute. For more information, see Specifying Identity Provider Attribute Mappings for Your User Pool.
Specifies whether a user pool attribute is required. If the attribute is required and the user doesn't provide a value, registration or sign-in will fail.
\",\ \"box\":true\ },\ \"NumberAttributeConstraints\":{\ \"shape\":\"NumberAttributeConstraintsType\",\ \"documentation\":\"Specifies the constraints for an attribute of the number type.
\"\ },\ \"StringAttributeConstraints\":{\ \"shape\":\"StringAttributeConstraintsType\",\ \"documentation\":\"Specifies the constraints for an attribute of the string type.
\"\ }\ },\ \"documentation\":\"Contains information about the schema attribute.
\"\ },\ \"SchemaAttributesListType\":{\ \"type\":\"list\",\ \"member\":{\"shape\":\"SchemaAttributeType\"},\ \"max\":50,\ \"min\":1\ },\ \"ScopeDoesNotExistException\":{\ \"type\":\"structure\",\ \"members\":{\ \"message\":{\"shape\":\"MessageType\"}\ },\ \"documentation\":\"This exception is thrown when the specified scope doesn't exist.
\",\ \"exception\":true\ },\ \"ScopeListType\":{\ \"type\":\"list\",\ \"member\":{\"shape\":\"ScopeType\"},\ \"max\":50\ },\ \"ScopeType\":{\ \"type\":\"string\",\ \"max\":256,\ \"min\":1,\ \"pattern\":\"[\\\\x21\\\\x23-\\\\x5B\\\\x5D-\\\\x7E]+\"\ },\ \"SearchPaginationTokenType\":{\ \"type\":\"string\",\ \"min\":1,\ \"pattern\":\"[\\\\S]+\"\ },\ \"SearchedAttributeNamesListType\":{\ \"type\":\"list\",\ \"member\":{\"shape\":\"AttributeNameType\"}\ },\ \"SecretCodeType\":{\ \"type\":\"string\",\ \"min\":16,\ \"pattern\":\"[A-Za-z0-9]+\",\ \"sensitive\":true\ },\ \"SecretHashType\":{\ \"type\":\"string\",\ \"max\":128,\ \"min\":1,\ \"pattern\":\"[\\\\w+=/]+\",\ \"sensitive\":true\ },\ \"SessionType\":{\ \"type\":\"string\",\ \"max\":2048,\ \"min\":20,\ \"sensitive\":true\ },\ \"SetRiskConfigurationRequest\":{\ \"type\":\"structure\",\ \"required\":[\"UserPoolId\"],\ \"members\":{\ \"UserPoolId\":{\ \"shape\":\"UserPoolIdType\",\ \"documentation\":\"The user pool ID.
\"\ },\ \"ClientId\":{\ \"shape\":\"ClientIdType\",\ \"documentation\":\"The app client ID. If ClientId
is null, then the risk configuration is mapped to userPoolId
. When the client ID is null, the same risk configuration is applied to all the clients in the userPool.
Otherwise, ClientId
is mapped to the client. When the client ID isn't null, the user pool configuration is overridden and the risk configuration for the client is used instead.
The compromised credentials risk configuration.
\"\ },\ \"AccountTakeoverRiskConfiguration\":{\ \"shape\":\"AccountTakeoverRiskConfigurationType\",\ \"documentation\":\"The account takeover risk configuration.
\"\ },\ \"RiskExceptionConfiguration\":{\ \"shape\":\"RiskExceptionConfigurationType\",\ \"documentation\":\"The configuration to override the risk decision.
\"\ }\ }\ },\ \"SetRiskConfigurationResponse\":{\ \"type\":\"structure\",\ \"required\":[\"RiskConfiguration\"],\ \"members\":{\ \"RiskConfiguration\":{\ \"shape\":\"RiskConfigurationType\",\ \"documentation\":\"The risk configuration.
\"\ }\ }\ },\ \"SetUICustomizationRequest\":{\ \"type\":\"structure\",\ \"required\":[\"UserPoolId\"],\ \"members\":{\ \"UserPoolId\":{\ \"shape\":\"UserPoolIdType\",\ \"documentation\":\"The user pool ID for the user pool.
\"\ },\ \"ClientId\":{\ \"shape\":\"ClientIdType\",\ \"documentation\":\"The client ID for the client app.
\"\ },\ \"CSS\":{\ \"shape\":\"CSSType\",\ \"documentation\":\"The CSS values in the UI customization.
\"\ },\ \"ImageFile\":{\ \"shape\":\"ImageFileType\",\ \"documentation\":\"The uploaded logo image for the UI customization.
\"\ }\ }\ },\ \"SetUICustomizationResponse\":{\ \"type\":\"structure\",\ \"required\":[\"UICustomization\"],\ \"members\":{\ \"UICustomization\":{\ \"shape\":\"UICustomizationType\",\ \"documentation\":\"The UI customization information.
\"\ }\ }\ },\ \"SetUserMFAPreferenceRequest\":{\ \"type\":\"structure\",\ \"required\":[\"AccessToken\"],\ \"members\":{\ \"SMSMfaSettings\":{\ \"shape\":\"SMSMfaSettingsType\",\ \"documentation\":\"The SMS text message multi-factor authentication (MFA) settings.
\"\ },\ \"SoftwareTokenMfaSettings\":{\ \"shape\":\"SoftwareTokenMfaSettingsType\",\ \"documentation\":\"The time-based one-time password (TOTP) software token MFA settings.
\"\ },\ \"AccessToken\":{\ \"shape\":\"TokenModelType\",\ \"documentation\":\"A valid access token that Amazon Cognito issued to the user whose MFA preference you want to set.
\"\ }\ }\ },\ \"SetUserMFAPreferenceResponse\":{\ \"type\":\"structure\",\ \"members\":{\ }\ },\ \"SetUserPoolMfaConfigRequest\":{\ \"type\":\"structure\",\ \"required\":[\"UserPoolId\"],\ \"members\":{\ \"UserPoolId\":{\ \"shape\":\"UserPoolIdType\",\ \"documentation\":\"The user pool ID.
\"\ },\ \"SmsMfaConfiguration\":{\ \"shape\":\"SmsMfaConfigType\",\ \"documentation\":\"The SMS text message MFA configuration.
\"\ },\ \"SoftwareTokenMfaConfiguration\":{\ \"shape\":\"SoftwareTokenMfaConfigType\",\ \"documentation\":\"The software token MFA configuration.
\"\ },\ \"MfaConfiguration\":{\ \"shape\":\"UserPoolMfaType\",\ \"documentation\":\"The MFA configuration. If you set the MfaConfiguration value to âONâ, only users who have set up an MFA factor can sign in. To learn more, see Adding Multi-Factor Authentication (MFA) to a user pool. Valid values include:
OFF
MFA won't be used for any users.
ON
MFA is required for all users to sign in.
OPTIONAL
MFA will be required only for individual users who have an MFA factor activated.
The SMS text message MFA configuration.
\"\ },\ \"SoftwareTokenMfaConfiguration\":{\ \"shape\":\"SoftwareTokenMfaConfigType\",\ \"documentation\":\"The software token MFA configuration.
\"\ },\ \"MfaConfiguration\":{\ \"shape\":\"UserPoolMfaType\",\ \"documentation\":\"The MFA configuration. Valid values include:
OFF
MFA won't be used for any users.
ON
MFA is required for all users to sign in.
OPTIONAL
MFA will be required only for individual users who have an MFA factor enabled.
A valid access token that Amazon Cognito issued to the user whose user settings you want to configure.
\"\ },\ \"MFAOptions\":{\ \"shape\":\"MFAOptionListType\",\ \"documentation\":\"You can use this parameter only to set an SMS configuration that uses SMS for delivery.
\"\ }\ },\ \"documentation\":\"Represents the request to set user settings.
\"\ },\ \"SetUserSettingsResponse\":{\ \"type\":\"structure\",\ \"members\":{\ },\ \"documentation\":\"The response from the server for a set user settings request.
\"\ },\ \"SignUpRequest\":{\ \"type\":\"structure\",\ \"required\":[\ \"ClientId\",\ \"Username\",\ \"Password\"\ ],\ \"members\":{\ \"ClientId\":{\ \"shape\":\"ClientIdType\",\ \"documentation\":\"The ID of the client associated with the user pool.
\"\ },\ \"SecretHash\":{\ \"shape\":\"SecretHashType\",\ \"documentation\":\"A keyed-hash message authentication code (HMAC) calculated using the secret key of a user pool client and username plus the client ID in the message.
\"\ },\ \"Username\":{\ \"shape\":\"UsernameType\",\ \"documentation\":\"The user name of the user you want to register.
\"\ },\ \"Password\":{\ \"shape\":\"PasswordType\",\ \"documentation\":\"The password of the user you want to register.
\"\ },\ \"UserAttributes\":{\ \"shape\":\"AttributeListType\",\ \"documentation\":\"An array of name-value pairs representing user attributes.
For custom attributes, you must prepend the custom:
prefix to the attribute name.
The validation data in the request to register a user.
\"\ },\ \"AnalyticsMetadata\":{\ \"shape\":\"AnalyticsMetadataType\",\ \"documentation\":\"The Amazon Pinpoint analytics metadata that contributes to your metrics for SignUp
calls.
Contextual data about your user session, such as the device fingerprint, IP address, or location. Amazon Cognito advanced security evaluates the risk of an authentication event based on the context that your app generates and passes to Amazon Cognito when it makes API requests.
\"\ },\ \"ClientMetadata\":{\ \"shape\":\"ClientMetadataType\",\ \"documentation\":\"A map of custom key-value pairs that you can provide as input for any custom workflows that this action triggers.
You create custom workflows by assigning Lambda functions to user pool triggers. When you use the SignUp API action, Amazon Cognito invokes any functions that are assigned to the following triggers: pre sign-up, custom message, and post confirmation. When Amazon Cognito invokes any of these functions, it passes a JSON payload, which the function receives as input. This payload contains a clientMetadata
attribute, which provides the data that you assigned to the ClientMetadata parameter in your SignUp request. In your function code in Lambda, you can process the clientMetadata
value to enhance your workflow for your specific needs.
For more information, see Customizing user pool Workflows with Lambda Triggers in the Amazon Cognito Developer Guide.
When you use the ClientMetadata parameter, remember that Amazon Cognito won't do the following:
Store the ClientMetadata value. This data is available only to Lambda triggers that are assigned to a user pool to support custom workflows. If your user pool configuration doesn't include triggers, the ClientMetadata parameter serves no purpose.
Validate the ClientMetadata value.
Encrypt the ClientMetadata value. Don't use Amazon Cognito to provide sensitive information.
Represents the request to register a user.
\"\ },\ \"SignUpResponse\":{\ \"type\":\"structure\",\ \"required\":[\ \"UserConfirmed\",\ \"UserSub\"\ ],\ \"members\":{\ \"UserConfirmed\":{\ \"shape\":\"BooleanType\",\ \"documentation\":\"A response from the server indicating that a user registration has been confirmed.
\"\ },\ \"CodeDeliveryDetails\":{\ \"shape\":\"CodeDeliveryDetailsType\",\ \"documentation\":\"The code delivery details returned by the server response to the user registration request.
\"\ },\ \"UserSub\":{\ \"shape\":\"StringType\",\ \"documentation\":\"The UUID of the authenticated user. This isn't the same as username
.
The response from the server for a registration request.
\"\ },\ \"SkippedIPRangeListType\":{\ \"type\":\"list\",\ \"member\":{\"shape\":\"StringType\"},\ \"max\":200\ },\ \"SmsConfigurationType\":{\ \"type\":\"structure\",\ \"required\":[\"SnsCallerArn\"],\ \"members\":{\ \"SnsCallerArn\":{\ \"shape\":\"ArnType\",\ \"documentation\":\"The Amazon Resource Name (ARN) of the Amazon SNS caller. This is the ARN of the IAM role in your Amazon Web Services account that Amazon Cognito will use to send SMS messages. SMS messages are subject to a spending limit.
\"\ },\ \"ExternalId\":{\ \"shape\":\"StringType\",\ \"documentation\":\"The external ID provides additional security for your IAM role. You can use an ExternalId
with the IAM role that you use with Amazon SNS to send SMS messages for your user pool. If you provide an ExternalId
, your Amazon Cognito user pool includes it in the request to assume your IAM role. You can configure the role trust policy to require that Amazon Cognito, and any principal, provide the ExternalID
. If you use the Amazon Cognito Management Console to create a role for SMS multi-factor authentication (MFA), Amazon Cognito creates a role with the required permissions and a trust policy that demonstrates use of the ExternalId
.
For more information about the ExternalId
of a role, see How to use an external ID when granting access to your Amazon Web Services resources to a third party
The Amazon Web Services Region to use with Amazon SNS integration. You can choose the same Region as your user pool, or a supported Legacy Amazon SNS alternate Region.
Amazon Cognito resources in the Asia Pacific (Seoul) Amazon Web Services Region must use your Amazon SNS configuration in the Asia Pacific (Tokyo) Region. For more information, see SMS message settings for Amazon Cognito user pools.
\"\ }\ },\ \"documentation\":\"The SMS configuration type is the settings that your Amazon Cognito user pool must use to send an SMS message from your Amazon Web Services account through Amazon Simple Notification Service. To send SMS messages with Amazon SNS in the Amazon Web Services Region that you want, the Amazon Cognito user pool uses an Identity and Access Management (IAM) role in your Amazon Web Services account.
\"\ },\ \"SmsMfaConfigType\":{\ \"type\":\"structure\",\ \"members\":{\ \"SmsAuthenticationMessage\":{\ \"shape\":\"SmsVerificationMessageType\",\ \"documentation\":\"The SMS authentication message that will be sent to users with the code they must sign in. The message must contain the â{####}â placeholder, which is replaced with the code. If the message isn't included, and default message will be used.
\"\ },\ \"SmsConfiguration\":{\ \"shape\":\"SmsConfigurationType\",\ \"documentation\":\"The SMS configuration with the settings that your Amazon Cognito user pool must use to send an SMS message from your Amazon Web Services account through Amazon Simple Notification Service. To request Amazon SNS in the Amazon Web Services Region that you want, the Amazon Cognito user pool uses an Identity and Access Management (IAM) role that you provide for your Amazon Web Services account.
\"\ }\ },\ \"documentation\":\"The SMS text message multi-factor authentication (MFA) configuration type.
\"\ },\ \"SmsVerificationMessageType\":{\ \"type\":\"string\",\ \"max\":140,\ \"min\":6,\ \"pattern\":\".*\\\\{####\\\\}.*\"\ },\ \"SoftwareTokenMFANotFoundException\":{\ \"type\":\"structure\",\ \"members\":{\ \"message\":{\"shape\":\"MessageType\"}\ },\ \"documentation\":\"This exception is thrown when the software token time-based one-time password (TOTP) multi-factor authentication (MFA) isn't activated for the user pool.
\",\ \"exception\":true\ },\ \"SoftwareTokenMFAUserCodeType\":{\ \"type\":\"string\",\ \"max\":6,\ \"min\":6,\ \"pattern\":\"[0-9]+\",\ \"sensitive\":true\ },\ \"SoftwareTokenMfaConfigType\":{\ \"type\":\"structure\",\ \"members\":{\ \"Enabled\":{\ \"shape\":\"BooleanType\",\ \"documentation\":\"Specifies whether software token MFA is activated.
\"\ }\ },\ \"documentation\":\"The type used for enabling software token MFA at the user pool level.
\"\ },\ \"SoftwareTokenMfaSettingsType\":{\ \"type\":\"structure\",\ \"members\":{\ \"Enabled\":{\ \"shape\":\"BooleanType\",\ \"documentation\":\"Specifies whether software token MFA is activated. If an MFA type is activated for a user, the user will be prompted for MFA during all sign-in attempts, unless device tracking is turned on and the device has been trusted.
\"\ },\ \"PreferredMfa\":{\ \"shape\":\"BooleanType\",\ \"documentation\":\"Specifies whether software token MFA is the preferred MFA method.
\"\ }\ },\ \"documentation\":\"The type used for enabling software token MFA at the user level. If an MFA type is activated for a user, the user will be prompted for MFA during all sign-in attempts, unless device tracking is turned on and the device has been trusted. If you want MFA to be applied selectively based on the assessed risk level of sign-in attempts, deactivate MFA for users and turn on Adaptive Authentication for the user pool.
\"\ },\ \"StartUserImportJobRequest\":{\ \"type\":\"structure\",\ \"required\":[\ \"UserPoolId\",\ \"JobId\"\ ],\ \"members\":{\ \"UserPoolId\":{\ \"shape\":\"UserPoolIdType\",\ \"documentation\":\"The user pool ID for the user pool that the users are being imported into.
\"\ },\ \"JobId\":{\ \"shape\":\"UserImportJobIdType\",\ \"documentation\":\"The job ID for the user import job.
\"\ }\ },\ \"documentation\":\"Represents the request to start the user import job.
\"\ },\ \"StartUserImportJobResponse\":{\ \"type\":\"structure\",\ \"members\":{\ \"UserImportJob\":{\ \"shape\":\"UserImportJobType\",\ \"documentation\":\"The job object that represents the user import job.
\"\ }\ },\ \"documentation\":\"Represents the response from the server to the request to start the user import job.
\"\ },\ \"StatusType\":{\ \"type\":\"string\",\ \"enum\":[\ \"Enabled\",\ \"Disabled\"\ ]\ },\ \"StopUserImportJobRequest\":{\ \"type\":\"structure\",\ \"required\":[\ \"UserPoolId\",\ \"JobId\"\ ],\ \"members\":{\ \"UserPoolId\":{\ \"shape\":\"UserPoolIdType\",\ \"documentation\":\"The user pool ID for the user pool that the users are being imported into.
\"\ },\ \"JobId\":{\ \"shape\":\"UserImportJobIdType\",\ \"documentation\":\"The job ID for the user import job.
\"\ }\ },\ \"documentation\":\"Represents the request to stop the user import job.
\"\ },\ \"StopUserImportJobResponse\":{\ \"type\":\"structure\",\ \"members\":{\ \"UserImportJob\":{\ \"shape\":\"UserImportJobType\",\ \"documentation\":\"The job object that represents the user import job.
\"\ }\ },\ \"documentation\":\"Represents the response from the server to the request to stop the user import job.
\"\ },\ \"StringAttributeConstraintsType\":{\ \"type\":\"structure\",\ \"members\":{\ \"MinLength\":{\ \"shape\":\"StringType\",\ \"documentation\":\"The minimum length.
\"\ },\ \"MaxLength\":{\ \"shape\":\"StringType\",\ \"documentation\":\"The maximum length.
\"\ }\ },\ \"documentation\":\"The constraints associated with a string attribute.
\"\ },\ \"StringType\":{\"type\":\"string\"},\ \"SupportedIdentityProvidersListType\":{\ \"type\":\"list\",\ \"member\":{\"shape\":\"ProviderNameType\"}\ },\ \"TagKeysType\":{\ \"type\":\"string\",\ \"max\":128,\ \"min\":1\ },\ \"TagResourceRequest\":{\ \"type\":\"structure\",\ \"required\":[\ \"ResourceArn\",\ \"Tags\"\ ],\ \"members\":{\ \"ResourceArn\":{\ \"shape\":\"ArnType\",\ \"documentation\":\"The Amazon Resource Name (ARN) of the user pool to assign the tags to.
\"\ },\ \"Tags\":{\ \"shape\":\"UserPoolTagsType\",\ \"documentation\":\"The tags to assign to the user pool.
\"\ }\ }\ },\ \"TagResourceResponse\":{\ \"type\":\"structure\",\ \"members\":{\ }\ },\ \"TagValueType\":{\ \"type\":\"string\",\ \"max\":256,\ \"min\":0\ },\ \"TemporaryPasswordValidityDaysType\":{\ \"type\":\"integer\",\ \"max\":365,\ \"min\":0\ },\ \"TimeUnitsType\":{\ \"type\":\"string\",\ \"enum\":[\ \"seconds\",\ \"minutes\",\ \"hours\",\ \"days\"\ ]\ },\ \"TokenModelType\":{\ \"type\":\"string\",\ \"pattern\":\"[A-Za-z0-9-_=.]+\",\ \"sensitive\":true\ },\ \"TokenValidityUnitsType\":{\ \"type\":\"structure\",\ \"members\":{\ \"AccessToken\":{\ \"shape\":\"TimeUnitsType\",\ \"documentation\":\" A time unit of seconds
, minutes
, hours
, or days
for the value that you set in the AccessTokenValidity
parameter. The default AccessTokenValidity
time unit is hours.
A time unit of seconds
, minutes
, hours
, or days
for the value that you set in the IdTokenValidity
parameter. The default IdTokenValidity
time unit is hours.
A time unit of seconds
, minutes
, hours
, or days
for the value that you set in the RefreshTokenValidity
parameter. The default RefreshTokenValidity
time unit is days.
The data type TokenValidityUnits specifies the time units you use when you set the duration of ID, access, and refresh tokens.
\"\ },\ \"TooManyFailedAttemptsException\":{\ \"type\":\"structure\",\ \"members\":{\ \"message\":{\ \"shape\":\"MessageType\",\ \"documentation\":\"The message returned when Amazon Cognito returns a TooManyFailedAttempts
exception.
This exception is thrown when the user has made too many failed attempts for a given action, such as sign-in.
\",\ \"exception\":true\ },\ \"TooManyRequestsException\":{\ \"type\":\"structure\",\ \"members\":{\ \"message\":{\ \"shape\":\"MessageType\",\ \"documentation\":\"The message returned when the Amazon Cognito service returns a too many requests exception.
\"\ }\ },\ \"documentation\":\"This exception is thrown when the user has made too many requests for a given operation.
\",\ \"exception\":true\ },\ \"UICustomizationType\":{\ \"type\":\"structure\",\ \"members\":{\ \"UserPoolId\":{\ \"shape\":\"UserPoolIdType\",\ \"documentation\":\"The user pool ID for the user pool.
\"\ },\ \"ClientId\":{\ \"shape\":\"ClientIdType\",\ \"documentation\":\"The client ID for the client app.
\"\ },\ \"ImageUrl\":{\ \"shape\":\"ImageUrlType\",\ \"documentation\":\"The logo image for the UI customization.
\"\ },\ \"CSS\":{\ \"shape\":\"CSSType\",\ \"documentation\":\"The CSS values in the UI customization.
\"\ },\ \"CSSVersion\":{\ \"shape\":\"CSSVersionType\",\ \"documentation\":\"The CSS version number.
\"\ },\ \"LastModifiedDate\":{\ \"shape\":\"DateType\",\ \"documentation\":\"The last-modified date for the UI customization.
\"\ },\ \"CreationDate\":{\ \"shape\":\"DateType\",\ \"documentation\":\"The creation date for the UI customization.
\"\ }\ },\ \"documentation\":\"A container for the UI customization information for a user pool's built-in app UI.
\"\ },\ \"UnauthorizedException\":{\ \"type\":\"structure\",\ \"members\":{\ \"message\":{\"shape\":\"MessageType\"}\ },\ \"documentation\":\"Exception that is thrown when the request isn't authorized. This can happen due to an invalid access token in the request.
\",\ \"exception\":true\ },\ \"UnexpectedLambdaException\":{\ \"type\":\"structure\",\ \"members\":{\ \"message\":{\ \"shape\":\"MessageType\",\ \"documentation\":\"The message returned when Amazon Cognito returns an unexpected Lambda exception.
\"\ }\ },\ \"documentation\":\"This exception is thrown when Amazon Cognito encounters an unexpected exception with Lambda.
\",\ \"exception\":true\ },\ \"UnsupportedIdentityProviderException\":{\ \"type\":\"structure\",\ \"members\":{\ \"message\":{\"shape\":\"MessageType\"}\ },\ \"documentation\":\"This exception is thrown when the specified identifier isn't supported.
\",\ \"exception\":true\ },\ \"UnsupportedOperationException\":{\ \"type\":\"structure\",\ \"members\":{\ \"message\":{\"shape\":\"MessageType\"}\ },\ \"documentation\":\"Exception that is thrown when you attempt to perform an operation that isn't enabled for the user pool client.
\",\ \"exception\":true\ },\ \"UnsupportedTokenTypeException\":{\ \"type\":\"structure\",\ \"members\":{\ \"message\":{\"shape\":\"MessageType\"}\ },\ \"documentation\":\"Exception that is thrown when an unsupported token is passed to an operation.
\",\ \"exception\":true\ },\ \"UnsupportedUserStateException\":{\ \"type\":\"structure\",\ \"members\":{\ \"message\":{\ \"shape\":\"MessageType\",\ \"documentation\":\"The message returned when the user is in an unsupported state.
\"\ }\ },\ \"documentation\":\"The request failed because the user is in an unsupported state.
\",\ \"exception\":true\ },\ \"UntagResourceRequest\":{\ \"type\":\"structure\",\ \"required\":[\ \"ResourceArn\",\ \"TagKeys\"\ ],\ \"members\":{\ \"ResourceArn\":{\ \"shape\":\"ArnType\",\ \"documentation\":\"The Amazon Resource Name (ARN) of the user pool that the tags are assigned to.
\"\ },\ \"TagKeys\":{\ \"shape\":\"UserPoolTagsListType\",\ \"documentation\":\"The keys of the tags to remove from the user pool.
\"\ }\ }\ },\ \"UntagResourceResponse\":{\ \"type\":\"structure\",\ \"members\":{\ }\ },\ \"UpdateAuthEventFeedbackRequest\":{\ \"type\":\"structure\",\ \"required\":[\ \"UserPoolId\",\ \"Username\",\ \"EventId\",\ \"FeedbackToken\",\ \"FeedbackValue\"\ ],\ \"members\":{\ \"UserPoolId\":{\ \"shape\":\"UserPoolIdType\",\ \"documentation\":\"The user pool ID.
\"\ },\ \"Username\":{\ \"shape\":\"UsernameType\",\ \"documentation\":\"The user pool username.
\"\ },\ \"EventId\":{\ \"shape\":\"EventIdType\",\ \"documentation\":\"The event ID.
\"\ },\ \"FeedbackToken\":{\ \"shape\":\"TokenModelType\",\ \"documentation\":\"The feedback token.
\"\ },\ \"FeedbackValue\":{\ \"shape\":\"FeedbackValueType\",\ \"documentation\":\"The authentication event feedback value.
\"\ }\ }\ },\ \"UpdateAuthEventFeedbackResponse\":{\ \"type\":\"structure\",\ \"members\":{\ }\ },\ \"UpdateDeviceStatusRequest\":{\ \"type\":\"structure\",\ \"required\":[\ \"AccessToken\",\ \"DeviceKey\"\ ],\ \"members\":{\ \"AccessToken\":{\ \"shape\":\"TokenModelType\",\ \"documentation\":\"A valid access token that Amazon Cognito issued to the user whose device status you want to update.
\"\ },\ \"DeviceKey\":{\ \"shape\":\"DeviceKeyType\",\ \"documentation\":\"The device key.
\"\ },\ \"DeviceRememberedStatus\":{\ \"shape\":\"DeviceRememberedStatusType\",\ \"documentation\":\"The status of whether a device is remembered.
\"\ }\ },\ \"documentation\":\"Represents the request to update the device status.
\"\ },\ \"UpdateDeviceStatusResponse\":{\ \"type\":\"structure\",\ \"members\":{\ },\ \"documentation\":\"The response to the request to update the device status.
\"\ },\ \"UpdateGroupRequest\":{\ \"type\":\"structure\",\ \"required\":[\ \"GroupName\",\ \"UserPoolId\"\ ],\ \"members\":{\ \"GroupName\":{\ \"shape\":\"GroupNameType\",\ \"documentation\":\"The name of the group.
\"\ },\ \"UserPoolId\":{\ \"shape\":\"UserPoolIdType\",\ \"documentation\":\"The user pool ID for the user pool.
\"\ },\ \"Description\":{\ \"shape\":\"DescriptionType\",\ \"documentation\":\"A string containing the new description of the group.
\"\ },\ \"RoleArn\":{\ \"shape\":\"ArnType\",\ \"documentation\":\"The new role Amazon Resource Name (ARN) for the group. This is used for setting the cognito:roles
and cognito:preferred_role
claims in the token.
The new precedence value for the group. For more information about this parameter, see CreateGroup.
\"\ }\ }\ },\ \"UpdateGroupResponse\":{\ \"type\":\"structure\",\ \"members\":{\ \"Group\":{\ \"shape\":\"GroupType\",\ \"documentation\":\"The group object for the group.
\"\ }\ }\ },\ \"UpdateIdentityProviderRequest\":{\ \"type\":\"structure\",\ \"required\":[\ \"UserPoolId\",\ \"ProviderName\"\ ],\ \"members\":{\ \"UserPoolId\":{\ \"shape\":\"UserPoolIdType\",\ \"documentation\":\"The user pool ID.
\"\ },\ \"ProviderName\":{\ \"shape\":\"ProviderNameType\",\ \"documentation\":\"The IdP name.
\"\ },\ \"ProviderDetails\":{\ \"shape\":\"ProviderDetailsType\",\ \"documentation\":\"The IdP details to be updated, such as MetadataURL
and MetadataFile
.
The IdP attribute mapping to be changed.
\"\ },\ \"IdpIdentifiers\":{\ \"shape\":\"IdpIdentifiersListType\",\ \"documentation\":\"A list of IdP identifiers.
\"\ }\ }\ },\ \"UpdateIdentityProviderResponse\":{\ \"type\":\"structure\",\ \"required\":[\"IdentityProvider\"],\ \"members\":{\ \"IdentityProvider\":{\ \"shape\":\"IdentityProviderType\",\ \"documentation\":\"The identity provider details.
\"\ }\ }\ },\ \"UpdateResourceServerRequest\":{\ \"type\":\"structure\",\ \"required\":[\ \"UserPoolId\",\ \"Identifier\",\ \"Name\"\ ],\ \"members\":{\ \"UserPoolId\":{\ \"shape\":\"UserPoolIdType\",\ \"documentation\":\"The user pool ID for the user pool.
\"\ },\ \"Identifier\":{\ \"shape\":\"ResourceServerIdentifierType\",\ \"documentation\":\"The identifier for the resource server.
\"\ },\ \"Name\":{\ \"shape\":\"ResourceServerNameType\",\ \"documentation\":\"The name of the resource server.
\"\ },\ \"Scopes\":{\ \"shape\":\"ResourceServerScopeListType\",\ \"documentation\":\"The scope values to be set for the resource server.
\"\ }\ }\ },\ \"UpdateResourceServerResponse\":{\ \"type\":\"structure\",\ \"required\":[\"ResourceServer\"],\ \"members\":{\ \"ResourceServer\":{\ \"shape\":\"ResourceServerType\",\ \"documentation\":\"The resource server.
\"\ }\ }\ },\ \"UpdateUserAttributesRequest\":{\ \"type\":\"structure\",\ \"required\":[\ \"UserAttributes\",\ \"AccessToken\"\ ],\ \"members\":{\ \"UserAttributes\":{\ \"shape\":\"AttributeListType\",\ \"documentation\":\"An array of name-value pairs representing user attributes.
For custom attributes, you must prepend the custom:
prefix to the attribute name.
If you have set an attribute to require verification before Amazon Cognito updates its value, this request doesnât immediately update the value of that attribute. After your user receives and responds to a verification message to verify the new value, Amazon Cognito updates the attribute value. Your user can sign in and receive messages with the original attribute value until they verify the new value.
\"\ },\ \"AccessToken\":{\ \"shape\":\"TokenModelType\",\ \"documentation\":\"A valid access token that Amazon Cognito issued to the user whose user attributes you want to update.
\"\ },\ \"ClientMetadata\":{\ \"shape\":\"ClientMetadataType\",\ \"documentation\":\"A map of custom key-value pairs that you can provide as input for any custom workflows that this action initiates.
You create custom workflows by assigning Lambda functions to user pool triggers. When you use the UpdateUserAttributes API action, Amazon Cognito invokes the function that is assigned to the custom message trigger. When Amazon Cognito invokes this function, it passes a JSON payload, which the function receives as input. This payload contains a clientMetadata
attribute, which provides the data that you assigned to the ClientMetadata parameter in your UpdateUserAttributes request. In your function code in Lambda, you can process the clientMetadata
value to enhance your workflow for your specific needs.
For more information, see Customizing user pool Workflows with Lambda Triggers in the Amazon Cognito Developer Guide.
When you use the ClientMetadata parameter, remember that Amazon Cognito won't do the following:
Store the ClientMetadata value. This data is available only to Lambda triggers that are assigned to a user pool to support custom workflows. If your user pool configuration doesn't include triggers, the ClientMetadata parameter serves no purpose.
Validate the ClientMetadata value.
Encrypt the ClientMetadata value. Don't use Amazon Cognito to provide sensitive information.
Represents the request to update user attributes.
\"\ },\ \"UpdateUserAttributesResponse\":{\ \"type\":\"structure\",\ \"members\":{\ \"CodeDeliveryDetailsList\":{\ \"shape\":\"CodeDeliveryDetailsListType\",\ \"documentation\":\"The code delivery details list from the server for the request to update user attributes.
\"\ }\ },\ \"documentation\":\"Represents the response from the server for the request to update user attributes.
\"\ },\ \"UpdateUserPoolClientRequest\":{\ \"type\":\"structure\",\ \"required\":[\ \"UserPoolId\",\ \"ClientId\"\ ],\ \"members\":{\ \"UserPoolId\":{\ \"shape\":\"UserPoolIdType\",\ \"documentation\":\"The user pool ID for the user pool where you want to update the user pool client.
\"\ },\ \"ClientId\":{\ \"shape\":\"ClientIdType\",\ \"documentation\":\"The ID of the client associated with the user pool.
\"\ },\ \"ClientName\":{\ \"shape\":\"ClientNameType\",\ \"documentation\":\"The client name from the update user pool client request.
\"\ },\ \"RefreshTokenValidity\":{\ \"shape\":\"RefreshTokenValidityType\",\ \"documentation\":\"The refresh token time limit. After this limit expires, your user can't use their refresh token. To specify the time unit for RefreshTokenValidity
as seconds
, minutes
, hours
, or days
, set a TokenValidityUnits
value in your API request.
For example, when you set RefreshTokenValidity
as 10
and TokenValidityUnits
as days
, your user can refresh their session and retrieve new access and ID tokens for 10 days.
The default time unit for RefreshTokenValidity
in an API request is days. You can't set RefreshTokenValidity
to 0. If you do, Amazon Cognito overrides the value with the default value of 30 days. Valid range is displayed below in seconds.
If you don't specify otherwise in the configuration of your app client, your refresh tokens are valid for 30 days.
\"\ },\ \"AccessTokenValidity\":{\ \"shape\":\"AccessTokenValidityType\",\ \"documentation\":\"The access token time limit. After this limit expires, your user can't use their access token. To specify the time unit for AccessTokenValidity
as seconds
, minutes
, hours
, or days
, set a TokenValidityUnits
value in your API request.
For example, when you set AccessTokenValidity
to 10
and TokenValidityUnits
to hours
, your user can authorize access with their access token for 10 hours.
The default time unit for AccessTokenValidity
in an API request is hours. Valid range is displayed below in seconds.
If you don't specify otherwise in the configuration of your app client, your access tokens are valid for one hour.
\"\ },\ \"IdTokenValidity\":{\ \"shape\":\"IdTokenValidityType\",\ \"documentation\":\"The ID token time limit. After this limit expires, your user can't use their ID token. To specify the time unit for IdTokenValidity
as seconds
, minutes
, hours
, or days
, set a TokenValidityUnits
value in your API request.
For example, when you set IdTokenValidity
as 10
and TokenValidityUnits
as hours
, your user can authenticate their session with their ID token for 10 hours.
The default time unit for AccessTokenValidity
in an API request is hours. Valid range is displayed below in seconds.
If you don't specify otherwise in the configuration of your app client, your ID tokens are valid for one hour.
\"\ },\ \"TokenValidityUnits\":{\ \"shape\":\"TokenValidityUnitsType\",\ \"documentation\":\"The units in which the validity times are represented. The default unit for RefreshToken is days, and the default for ID and access tokens is hours.
\"\ },\ \"ReadAttributes\":{\ \"shape\":\"ClientPermissionListType\",\ \"documentation\":\"The read-only attributes of the user pool.
\"\ },\ \"WriteAttributes\":{\ \"shape\":\"ClientPermissionListType\",\ \"documentation\":\"The writeable attributes of the user pool.
\"\ },\ \"ExplicitAuthFlows\":{\ \"shape\":\"ExplicitAuthFlowsListType\",\ \"documentation\":\"The authentication flows that you want your user pool client to support. For each app client in your user pool, you can sign in your users with any combination of one or more flows, including with a user name and Secure Remote Password (SRP), a user name and password, or a custom authentication process that you define with Lambda functions.
If you don't specify a value for ExplicitAuthFlows
, your user client supports ALLOW_REFRESH_TOKEN_AUTH
, ALLOW_USER_SRP_AUTH
, and ALLOW_CUSTOM_AUTH
.
Valid values include:
ALLOW_ADMIN_USER_PASSWORD_AUTH
: Enable admin based user password authentication flow ADMIN_USER_PASSWORD_AUTH
. This setting replaces the ADMIN_NO_SRP_AUTH
setting. With this authentication flow, your app passes a user name and password to Amazon Cognito in the request, instead of using the Secure Remote Password (SRP) protocol to securely transmit the password.
ALLOW_CUSTOM_AUTH
: Enable Lambda trigger based authentication.
ALLOW_USER_PASSWORD_AUTH
: Enable user password-based authentication. In this flow, Amazon Cognito receives the password in the request instead of using the SRP protocol to verify passwords.
ALLOW_USER_SRP_AUTH
: Enable SRP-based authentication.
ALLOW_REFRESH_TOKEN_AUTH
: Enable authflow to refresh tokens.
In some environments, you will see the values ADMIN_NO_SRP_AUTH
, CUSTOM_AUTH_FLOW_ONLY
, or USER_PASSWORD_AUTH
. You can't assign these legacy ExplicitAuthFlows
values to user pool clients at the same time as values that begin with ALLOW_
, like ALLOW_USER_SRP_AUTH
.
A list of provider names for the IdPs that this client supports. The following are supported: COGNITO
, Facebook
, Google
, SignInWithApple
, LoginWithAmazon
, and the names of your own SAML and OIDC providers.
A list of allowed redirect (callback) URLs for the IdPs.
A redirect URI must:
Be an absolute URI.
Be registered with the authorization server.
Not include a fragment component.
See OAuth 2.0 - Redirection Endpoint.
Amazon Cognito requires HTTPS over HTTP except for http://localhost for testing purposes only.
App callback URLs such as myapp://example
are also supported.
A list of allowed logout URLs for the IdPs.
\"\ },\ \"DefaultRedirectURI\":{\ \"shape\":\"RedirectUrlType\",\ \"documentation\":\"The default redirect URI. Must be in the CallbackURLs
list.
A redirect URI must:
Be an absolute URI.
Be registered with the authorization server.
Not include a fragment component.
See OAuth 2.0 - Redirection Endpoint.
Amazon Cognito requires HTTPS over HTTP except for http://localhost
for testing purposes only.
App callback URLs such as myapp://example
are also supported.
The allowed OAuth flows.
Use a code grant flow, which provides an authorization code as the response. This code can be exchanged for access tokens with the /oauth2/token
endpoint.
Issue the access token (and, optionally, ID token, based on scopes) directly to your user.
Issue the access token from the /oauth2/token
endpoint directly to a non-person user using a combination of the client ID and client secret.
The allowed OAuth scopes. Possible values provided by OAuth are phone
, email
, openid
, and profile
. Possible values provided by Amazon Web Services are aws.cognito.signin.user.admin
. Custom scopes created in Resource Servers are also supported.
Set to true if the client is allowed to follow the OAuth protocol when interacting with Amazon Cognito user pools.
\"\ },\ \"AnalyticsConfiguration\":{\ \"shape\":\"AnalyticsConfigurationType\",\ \"documentation\":\"The Amazon Pinpoint analytics configuration necessary to collect metrics for this user pool.
In Amazon Web Services Regions where Amazon Pinpoint isn't available, user pools only support sending events to Amazon Pinpoint projects in us-east-1. In Regions where Amazon Pinpoint is available, user pools support sending events to Amazon Pinpoint projects within that same Region.
Errors and responses that you want Amazon Cognito APIs to return during authentication, account confirmation, and password recovery when the user doesn't exist in the user pool. When set to ENABLED
and the user doesn't exist, authentication returns an error indicating either the username or password was incorrect. Account confirmation and password recovery return a response indicating a code was sent to a simulated destination. When set to LEGACY
, those APIs return a UserNotFoundException
exception if the user doesn't exist in the user pool.
Valid values include:
ENABLED
- This prevents user existence-related errors.
LEGACY
- This represents the early behavior of Amazon Cognito where user existence related errors aren't prevented.
Activates or deactivates token revocation. For more information about revoking tokens, see RevokeToken.
\"\ },\ \"EnablePropagateAdditionalUserContextData\":{\ \"shape\":\"WrappedBooleanType\",\ \"documentation\":\"Activates the propagation of additional user context data. For more information about propagation of user context data, see Adding advanced security to a user pool. If you donât include this parameter, you can't send device fingerprint information, including source IP address, to Amazon Cognito advanced security. You can only activate EnablePropagateAdditionalUserContextData
in an app client that has a client secret.
Amazon Cognito creates a session token for each API request in an authentication flow. AuthSessionValidity
is the duration, in minutes, of that session token. Your user pool native user must respond to each authentication challenge before the session expires.
Represents the request to update the user pool client.
\"\ },\ \"UpdateUserPoolClientResponse\":{\ \"type\":\"structure\",\ \"members\":{\ \"UserPoolClient\":{\ \"shape\":\"UserPoolClientType\",\ \"documentation\":\"The user pool client value from the response from the server when you request to update the user pool client.
\"\ }\ },\ \"documentation\":\"Represents the response from the server to the request to update the user pool client.
\"\ },\ \"UpdateUserPoolDomainRequest\":{\ \"type\":\"structure\",\ \"required\":[\ \"Domain\",\ \"UserPoolId\",\ \"CustomDomainConfig\"\ ],\ \"members\":{\ \"Domain\":{\ \"shape\":\"DomainType\",\ \"documentation\":\"The domain name for the custom domain that hosts the sign-up and sign-in pages for your application. One example might be auth.example.com
.
This string can include only lowercase letters, numbers, and hyphens. Don't use a hyphen for the first or last character. Use periods to separate subdomain names.
\"\ },\ \"UserPoolId\":{\ \"shape\":\"UserPoolIdType\",\ \"documentation\":\"The ID of the user pool that is associated with the custom domain whose certificate you're updating.
\"\ },\ \"CustomDomainConfig\":{\ \"shape\":\"CustomDomainConfigType\",\ \"documentation\":\"The configuration for a custom domain that hosts the sign-up and sign-in pages for your application. Use this object to specify an SSL certificate that is managed by ACM.
\"\ }\ },\ \"documentation\":\"The UpdateUserPoolDomain request input.
\"\ },\ \"UpdateUserPoolDomainResponse\":{\ \"type\":\"structure\",\ \"members\":{\ \"CloudFrontDomain\":{\ \"shape\":\"DomainType\",\ \"documentation\":\"The Amazon CloudFront endpoint that Amazon Cognito set up when you added the custom domain to your user pool.
\"\ }\ },\ \"documentation\":\"The UpdateUserPoolDomain response output.
\"\ },\ \"UpdateUserPoolRequest\":{\ \"type\":\"structure\",\ \"required\":[\"UserPoolId\"],\ \"members\":{\ \"UserPoolId\":{\ \"shape\":\"UserPoolIdType\",\ \"documentation\":\"The user pool ID for the user pool you want to update.
\"\ },\ \"Policies\":{\ \"shape\":\"UserPoolPolicyType\",\ \"documentation\":\"A container with the policies you want to update in a user pool.
\"\ },\ \"DeletionProtection\":{\ \"shape\":\"DeletionProtectionType\",\ \"documentation\":\"When active, DeletionProtection
prevents accidental deletion of your user pool. Before you can delete a user pool that you have protected against deletion, you must deactivate this feature.
When you try to delete a protected user pool in a DeleteUserPool
API request, Amazon Cognito returns an InvalidParameterException
error. To delete a protected user pool, send a new DeleteUserPool
request after you deactivate deletion protection in an UpdateUserPool
API request.
The Lambda configuration information from the request to update the user pool.
\"\ },\ \"AutoVerifiedAttributes\":{\ \"shape\":\"VerifiedAttributesListType\",\ \"documentation\":\"The attributes that are automatically verified when Amazon Cognito requests to update user pools.
\"\ },\ \"SmsVerificationMessage\":{\ \"shape\":\"SmsVerificationMessageType\",\ \"documentation\":\"This parameter is no longer used. See VerificationMessageTemplateType.
\"\ },\ \"EmailVerificationMessage\":{\ \"shape\":\"EmailVerificationMessageType\",\ \"documentation\":\"This parameter is no longer used. See VerificationMessageTemplateType.
\"\ },\ \"EmailVerificationSubject\":{\ \"shape\":\"EmailVerificationSubjectType\",\ \"documentation\":\"This parameter is no longer used. See VerificationMessageTemplateType.
\"\ },\ \"VerificationMessageTemplate\":{\ \"shape\":\"VerificationMessageTemplateType\",\ \"documentation\":\"The template for verification messages.
\"\ },\ \"SmsAuthenticationMessage\":{\ \"shape\":\"SmsVerificationMessageType\",\ \"documentation\":\"The contents of the SMS authentication message.
\"\ },\ \"UserAttributeUpdateSettings\":{\ \"shape\":\"UserAttributeUpdateSettingsType\",\ \"documentation\":\"The settings for updates to user attributes. These settings include the property AttributesRequireVerificationBeforeUpdate
, a user-pool setting that tells Amazon Cognito how to handle changes to the value of your users' email address and phone number attributes. For more information, see Verifying updates to email addresses and phone numbers.
Possible values include:
OFF
- MFA tokens aren't required and can't be specified during user registration.
ON
- MFA tokens are required for all user registrations. You can only specify ON when you're initially creating a user pool. You can use the SetUserPoolMfaConfig API operation to turn MFA \\\"ON\\\" for existing user pools.
OPTIONAL
- Users have the option when registering to create an MFA token.
The device-remembering configuration for a user pool. A null value indicates that you have deactivated device remembering in your user pool.
When you provide a value for any DeviceConfiguration
field, you activate the Amazon Cognito device-remembering feature.
The email configuration of your user pool. The email configuration type sets your preferred sending method, Amazon Web Services Region, and sender for email invitation and verification messages from your user pool.
\"\ },\ \"SmsConfiguration\":{\ \"shape\":\"SmsConfigurationType\",\ \"documentation\":\"The SMS configuration with the settings that your Amazon Cognito user pool must use to send an SMS message from your Amazon Web Services account through Amazon Simple Notification Service. To send SMS messages with Amazon SNS in the Amazon Web Services Region that you want, the Amazon Cognito user pool uses an Identity and Access Management (IAM) role in your Amazon Web Services account.
\"\ },\ \"UserPoolTags\":{\ \"shape\":\"UserPoolTagsType\",\ \"documentation\":\"The tag keys and values to assign to the user pool. A tag is a label that you can use to categorize and manage user pools in different ways, such as by purpose, owner, environment, or other criteria.
\"\ },\ \"AdminCreateUserConfig\":{\ \"shape\":\"AdminCreateUserConfigType\",\ \"documentation\":\"The configuration for AdminCreateUser
requests.
Enables advanced security risk detection. Set the key AdvancedSecurityMode
to the value \\\"AUDIT\\\".
The available verified method a user can use to recover their password when they call ForgotPassword
. You can use this setting to define a preferred method when a user has more than one method available. With this setting, SMS doesn't qualify for a valid password recovery mechanism if the user also has SMS multi-factor authentication (MFA) activated. In the absence of this setting, Amazon Cognito uses the legacy behavior to determine the recovery method where SMS is preferred through email.
Represents the request to update the user pool.
\"\ },\ \"UpdateUserPoolResponse\":{\ \"type\":\"structure\",\ \"members\":{\ },\ \"documentation\":\"Represents the response from the server when you make a request to update the user pool.
\"\ },\ \"UserAttributeUpdateSettingsType\":{\ \"type\":\"structure\",\ \"members\":{\ \"AttributesRequireVerificationBeforeUpdate\":{\ \"shape\":\"AttributesRequireVerificationBeforeUpdateType\",\ \"documentation\":\"Requires that your user verifies their email address, phone number, or both before Amazon Cognito updates the value of that attribute. When you update a user attribute that has this option activated, Amazon Cognito sends a verification message to the new phone number or email address. Amazon Cognito doesnât change the value of the attribute until your user responds to the verification message and confirms the new value.
You can verify an updated email address or phone number with a VerifyUserAttribute API request. You can also call the UpdateUserAttributes or AdminUpdateUserAttributes API and set email_verified
or phone_number_verified
to true.
When AttributesRequireVerificationBeforeUpdate
is false, your user pool doesn't require that your users verify attribute changes before Amazon Cognito updates them. In a user pool where AttributesRequireVerificationBeforeUpdate
is false, API operations that change attribute values can immediately update a userâs email
or phone_number
attribute.
The settings for updates to user attributes. These settings include the property AttributesRequireVerificationBeforeUpdate
, a user-pool setting that tells Amazon Cognito how to handle changes to the value of your users' email address and phone number attributes. For more information, see Verifying updates to email addresses and phone numbers.
The source IP address of your user's device.
\"\ },\ \"EncodedData\":{\ \"shape\":\"StringType\",\ \"documentation\":\"Encoded device-fingerprint details that your app collected with the Amazon Cognito context data collection library. For more information, see Adding user device and session data to API requests.
\"\ }\ },\ \"documentation\":\"Contextual data, such as the user's device fingerprint, IP address, or location, used for evaluating the risk of an unexpected event by Amazon Cognito advanced security.
\",\ \"sensitive\":true\ },\ \"UserFilterType\":{\ \"type\":\"string\",\ \"max\":256\ },\ \"UserImportInProgressException\":{\ \"type\":\"structure\",\ \"members\":{\ \"message\":{\ \"shape\":\"MessageType\",\ \"documentation\":\"The message returned when the user pool has an import job running.
\"\ }\ },\ \"documentation\":\"This exception is thrown when you're trying to modify a user pool while a user import job is in progress for that pool.
\",\ \"exception\":true\ },\ \"UserImportJobIdType\":{\ \"type\":\"string\",\ \"max\":55,\ \"min\":1,\ \"pattern\":\"import-[0-9a-zA-Z-]+\"\ },\ \"UserImportJobNameType\":{\ \"type\":\"string\",\ \"max\":128,\ \"min\":1,\ \"pattern\":\"[\\\\w\\\\s+=,.@-]+\"\ },\ \"UserImportJobStatusType\":{\ \"type\":\"string\",\ \"enum\":[\ \"Created\",\ \"Pending\",\ \"InProgress\",\ \"Stopping\",\ \"Expired\",\ \"Stopped\",\ \"Failed\",\ \"Succeeded\"\ ]\ },\ \"UserImportJobType\":{\ \"type\":\"structure\",\ \"members\":{\ \"JobName\":{\ \"shape\":\"UserImportJobNameType\",\ \"documentation\":\"The job name for the user import job.
\"\ },\ \"JobId\":{\ \"shape\":\"UserImportJobIdType\",\ \"documentation\":\"The job ID for the user import job.
\"\ },\ \"UserPoolId\":{\ \"shape\":\"UserPoolIdType\",\ \"documentation\":\"The user pool ID for the user pool that the users are being imported into.
\"\ },\ \"PreSignedUrl\":{\ \"shape\":\"PreSignedUrlType\",\ \"documentation\":\"The pre-signed URL to be used to upload the .csv
file.
The date the user import job was created.
\"\ },\ \"StartDate\":{\ \"shape\":\"DateType\",\ \"documentation\":\"The date when the user import job was started.
\"\ },\ \"CompletionDate\":{\ \"shape\":\"DateType\",\ \"documentation\":\"The date when the user import job was completed.
\"\ },\ \"Status\":{\ \"shape\":\"UserImportJobStatusType\",\ \"documentation\":\"The status of the user import job. One of the following:
Created
- The job was created but not started.
Pending
- A transition state. You have started the job, but it has not begun importing users yet.
InProgress
- The job has started, and users are being imported.
Stopping
- You have stopped the job, but the job has not stopped importing users yet.
Stopped
- You have stopped the job, and the job has stopped importing users.
Succeeded
- The job has completed successfully.
Failed
- The job has stopped due to an error.
Expired
- You created a job, but did not start the job within 24-48 hours. All data associated with the job was deleted, and the job can't be started.
The role Amazon Resource Name (ARN) for the Amazon CloudWatch Logging role for the user import job. For more information, see \\\"Creating the CloudWatch Logs IAM Role\\\" in the Amazon Cognito Developer Guide.
\"\ },\ \"ImportedUsers\":{\ \"shape\":\"LongType\",\ \"documentation\":\"The number of users that were successfully imported.
\"\ },\ \"SkippedUsers\":{\ \"shape\":\"LongType\",\ \"documentation\":\"The number of users that were skipped.
\"\ },\ \"FailedUsers\":{\ \"shape\":\"LongType\",\ \"documentation\":\"The number of users that couldn't be imported.
\"\ },\ \"CompletionMessage\":{\ \"shape\":\"CompletionMessageType\",\ \"documentation\":\"The message returned when the user import job is completed.
\"\ }\ },\ \"documentation\":\"The user import job type.
\"\ },\ \"UserImportJobsListType\":{\ \"type\":\"list\",\ \"member\":{\"shape\":\"UserImportJobType\"},\ \"max\":50,\ \"min\":1\ },\ \"UserLambdaValidationException\":{\ \"type\":\"structure\",\ \"members\":{\ \"message\":{\ \"shape\":\"MessageType\",\ \"documentation\":\"The message returned when the Amazon Cognito service returns a user validation exception with the Lambda service.
\"\ }\ },\ \"documentation\":\"This exception is thrown when the Amazon Cognito service encounters a user validation exception with the Lambda service.
\",\ \"exception\":true\ },\ \"UserMFASettingListType\":{\ \"type\":\"list\",\ \"member\":{\"shape\":\"StringType\"}\ },\ \"UserNotConfirmedException\":{\ \"type\":\"structure\",\ \"members\":{\ \"message\":{\ \"shape\":\"MessageType\",\ \"documentation\":\"The message returned when a user isn't confirmed successfully.
\"\ }\ },\ \"documentation\":\"This exception is thrown when a user isn't confirmed successfully.
\",\ \"exception\":true\ },\ \"UserNotFoundException\":{\ \"type\":\"structure\",\ \"members\":{\ \"message\":{\ \"shape\":\"MessageType\",\ \"documentation\":\"The message returned when a user isn't found.
\"\ }\ },\ \"documentation\":\"This exception is thrown when a user isn't found.
\",\ \"exception\":true\ },\ \"UserPoolAddOnNotEnabledException\":{\ \"type\":\"structure\",\ \"members\":{\ \"message\":{\"shape\":\"MessageType\"}\ },\ \"documentation\":\"This exception is thrown when user pool add-ons aren't enabled.
\",\ \"exception\":true\ },\ \"UserPoolAddOnsType\":{\ \"type\":\"structure\",\ \"required\":[\"AdvancedSecurityMode\"],\ \"members\":{\ \"AdvancedSecurityMode\":{\ \"shape\":\"AdvancedSecurityModeType\",\ \"documentation\":\"The advanced security mode.
\"\ }\ },\ \"documentation\":\"The user pool add-ons type.
\"\ },\ \"UserPoolClientDescription\":{\ \"type\":\"structure\",\ \"members\":{\ \"ClientId\":{\ \"shape\":\"ClientIdType\",\ \"documentation\":\"The ID of the client associated with the user pool.
\"\ },\ \"UserPoolId\":{\ \"shape\":\"UserPoolIdType\",\ \"documentation\":\"The user pool ID for the user pool where you want to describe the user pool client.
\"\ },\ \"ClientName\":{\ \"shape\":\"ClientNameType\",\ \"documentation\":\"The client name from the user pool client description.
\"\ }\ },\ \"documentation\":\"The description of the user pool client.
\"\ },\ \"UserPoolClientListType\":{\ \"type\":\"list\",\ \"member\":{\"shape\":\"UserPoolClientDescription\"}\ },\ \"UserPoolClientType\":{\ \"type\":\"structure\",\ \"members\":{\ \"UserPoolId\":{\ \"shape\":\"UserPoolIdType\",\ \"documentation\":\"The user pool ID for the user pool client.
\"\ },\ \"ClientName\":{\ \"shape\":\"ClientNameType\",\ \"documentation\":\"The client name from the user pool request of the client type.
\"\ },\ \"ClientId\":{\ \"shape\":\"ClientIdType\",\ \"documentation\":\"The ID of the client associated with the user pool.
\"\ },\ \"ClientSecret\":{\ \"shape\":\"ClientSecretType\",\ \"documentation\":\"The client secret from the user pool request of the client type.
\"\ },\ \"LastModifiedDate\":{\ \"shape\":\"DateType\",\ \"documentation\":\"The date the user pool client was last modified.
\"\ },\ \"CreationDate\":{\ \"shape\":\"DateType\",\ \"documentation\":\"The date the user pool client was created.
\"\ },\ \"RefreshTokenValidity\":{\ \"shape\":\"RefreshTokenValidityType\",\ \"documentation\":\"The refresh token time limit. After this limit expires, your user can't use their refresh token. To specify the time unit for RefreshTokenValidity
as seconds
, minutes
, hours
, or days
, set a TokenValidityUnits
value in your API request.
For example, when you set RefreshTokenValidity
as 10
and TokenValidityUnits
as days
, your user can refresh their session and retrieve new access and ID tokens for 10 days.
The default time unit for RefreshTokenValidity
in an API request is days. You can't set RefreshTokenValidity
to 0. If you do, Amazon Cognito overrides the value with the default value of 30 days. Valid range is displayed below in seconds.
If you don't specify otherwise in the configuration of your app client, your refresh tokens are valid for 30 days.
\"\ },\ \"AccessTokenValidity\":{\ \"shape\":\"AccessTokenValidityType\",\ \"documentation\":\"The access token time limit. After this limit expires, your user can't use their access token. To specify the time unit for AccessTokenValidity
as seconds
, minutes
, hours
, or days
, set a TokenValidityUnits
value in your API request.
For example, when you set AccessTokenValidity
to 10
and TokenValidityUnits
to hours
, your user can authorize access with their access token for 10 hours.
The default time unit for AccessTokenValidity
in an API request is hours. Valid range is displayed below in seconds.
If you don't specify otherwise in the configuration of your app client, your access tokens are valid for one hour.
\"\ },\ \"IdTokenValidity\":{\ \"shape\":\"IdTokenValidityType\",\ \"documentation\":\"The ID token time limit. After this limit expires, your user can't use their ID token. To specify the time unit for IdTokenValidity
as seconds
, minutes
, hours
, or days
, set a TokenValidityUnits
value in your API request.
For example, when you set IdTokenValidity
as 10
and TokenValidityUnits
as hours
, your user can authenticate their session with their ID token for 10 hours.
The default time unit for AccessTokenValidity
in an API request is hours. Valid range is displayed below in seconds.
If you don't specify otherwise in the configuration of your app client, your ID tokens are valid for one hour.
\"\ },\ \"TokenValidityUnits\":{\ \"shape\":\"TokenValidityUnitsType\",\ \"documentation\":\"The time units used to specify the token validity times of each token type: ID, access, and refresh.
\"\ },\ \"ReadAttributes\":{\ \"shape\":\"ClientPermissionListType\",\ \"documentation\":\"The Read-only attributes.
\"\ },\ \"WriteAttributes\":{\ \"shape\":\"ClientPermissionListType\",\ \"documentation\":\"The writeable attributes.
\"\ },\ \"ExplicitAuthFlows\":{\ \"shape\":\"ExplicitAuthFlowsListType\",\ \"documentation\":\"The authentication flows that you want your user pool client to support. For each app client in your user pool, you can sign in your users with any combination of one or more flows, including with a user name and Secure Remote Password (SRP), a user name and password, or a custom authentication process that you define with Lambda functions.
If you don't specify a value for ExplicitAuthFlows
, your user client supports ALLOW_REFRESH_TOKEN_AUTH
, ALLOW_USER_SRP_AUTH
, and ALLOW_CUSTOM_AUTH
.
Valid values include:
ALLOW_ADMIN_USER_PASSWORD_AUTH
: Enable admin based user password authentication flow ADMIN_USER_PASSWORD_AUTH
. This setting replaces the ADMIN_NO_SRP_AUTH
setting. With this authentication flow, your app passes a user name and password to Amazon Cognito in the request, instead of using the Secure Remote Password (SRP) protocol to securely transmit the password.
ALLOW_CUSTOM_AUTH
: Enable Lambda trigger based authentication.
ALLOW_USER_PASSWORD_AUTH
: Enable user password-based authentication. In this flow, Amazon Cognito receives the password in the request instead of using the SRP protocol to verify passwords.
ALLOW_USER_SRP_AUTH
: Enable SRP-based authentication.
ALLOW_REFRESH_TOKEN_AUTH
: Enable authflow to refresh tokens.
In some environments, you will see the values ADMIN_NO_SRP_AUTH
, CUSTOM_AUTH_FLOW_ONLY
, or USER_PASSWORD_AUTH
. You can't assign these legacy ExplicitAuthFlows
values to user pool clients at the same time as values that begin with ALLOW_
, like ALLOW_USER_SRP_AUTH
.
A list of provider names for the IdPs that this client supports. The following are supported: COGNITO
, Facebook
, Google
, SignInWithApple
, LoginWithAmazon
, and the names of your own SAML and OIDC providers.
A list of allowed redirect (callback) URLs for the IdPs.
A redirect URI must:
Be an absolute URI.
Be registered with the authorization server.
Not include a fragment component.
See OAuth 2.0 - Redirection Endpoint.
Amazon Cognito requires HTTPS over HTTP except for http://localhost for testing purposes only.
App callback URLs such as myapp://example are also supported.
\"\ },\ \"LogoutURLs\":{\ \"shape\":\"LogoutURLsListType\",\ \"documentation\":\"A list of allowed logout URLs for the IdPs.
\"\ },\ \"DefaultRedirectURI\":{\ \"shape\":\"RedirectUrlType\",\ \"documentation\":\"The default redirect URI. Must be in the CallbackURLs
list.
A redirect URI must:
Be an absolute URI.
Be registered with the authorization server.
Not include a fragment component.
See OAuth 2.0 - Redirection Endpoint.
Amazon Cognito requires HTTPS over HTTP except for http://localhost for testing purposes only.
App callback URLs such as myapp://example are also supported.
\"\ },\ \"AllowedOAuthFlows\":{\ \"shape\":\"OAuthFlowsType\",\ \"documentation\":\"The allowed OAuth flows.
Use a code grant flow, which provides an authorization code as the response. This code can be exchanged for access tokens with the /oauth2/token
endpoint.
Issue the access token (and, optionally, ID token, based on scopes) directly to your user.
Issue the access token from the /oauth2/token
endpoint directly to a non-person user using a combination of the client ID and client secret.
The OAuth scopes that your app client supports. Possible values that OAuth provides are phone
, email
, openid
, and profile
. Possible values that Amazon Web Services provides are aws.cognito.signin.user.admin
. Amazon Cognito also supports custom scopes that you create in Resource Servers.
Set to true if the client is allowed to follow the OAuth protocol when interacting with Amazon Cognito user pools.
\",\ \"box\":true\ },\ \"AnalyticsConfiguration\":{\ \"shape\":\"AnalyticsConfigurationType\",\ \"documentation\":\"The Amazon Pinpoint analytics configuration for the user pool client.
Amazon Cognito user pools only support sending events to Amazon Pinpoint projects in the US East (N. Virginia) us-east-1 Region, regardless of the Region where the user pool resides.
Errors and responses that you want Amazon Cognito APIs to return during authentication, account confirmation, and password recovery when the user doesn't exist in the user pool. When set to ENABLED
and the user doesn't exist, authentication returns an error indicating either the username or password was incorrect. Account confirmation and password recovery return a response indicating a code was sent to a simulated destination. When set to LEGACY
, those APIs return a UserNotFoundException
exception if the user doesn't exist in the user pool.
Valid values include:
ENABLED
- This prevents user existence-related errors.
LEGACY
- This represents the old behavior of Amazon Cognito where user existence related errors aren't prevented.
Indicates whether token revocation is activated for the user pool client. When you create a new user pool client, token revocation is activated by default. For more information about revoking tokens, see RevokeToken.
\"\ },\ \"EnablePropagateAdditionalUserContextData\":{\ \"shape\":\"WrappedBooleanType\",\ \"documentation\":\"When EnablePropagateAdditionalUserContextData
is true, Amazon Cognito accepts an IpAddress
value that you send in the UserContextData
parameter. The UserContextData
parameter sends information to Amazon Cognito advanced security for risk analysis. You can send UserContextData
when you sign in Amazon Cognito native users with the InitiateAuth
and RespondToAuthChallenge
API operations.
When EnablePropagateAdditionalUserContextData
is false, you can't send your user's source IP address to Amazon Cognito advanced security with unauthenticated API operations. EnablePropagateAdditionalUserContextData
doesn't affect whether you can send a source IP address in a ContextData
parameter with the authenticated API operations AdminInitiateAuth
and AdminRespondToAuthChallenge
.
You can only activate EnablePropagateAdditionalUserContextData
in an app client that has a client secret. For more information about propagation of user context data, see Adding user device and session data to API requests.
Amazon Cognito creates a session token for each API request in an authentication flow. AuthSessionValidity
is the duration, in minutes, of that session token. Your user pool native user must respond to each authentication challenge before the session expires.
Contains information about a user pool client.
\"\ },\ \"UserPoolDescriptionType\":{\ \"type\":\"structure\",\ \"members\":{\ \"Id\":{\ \"shape\":\"UserPoolIdType\",\ \"documentation\":\"The ID in a user pool description.
\"\ },\ \"Name\":{\ \"shape\":\"UserPoolNameType\",\ \"documentation\":\"The name in a user pool description.
\"\ },\ \"LambdaConfig\":{\ \"shape\":\"LambdaConfigType\",\ \"documentation\":\"The Lambda configuration information in a user pool description.
\"\ },\ \"Status\":{\ \"shape\":\"StatusType\",\ \"documentation\":\"The user pool status in a user pool description.
\"\ },\ \"LastModifiedDate\":{\ \"shape\":\"DateType\",\ \"documentation\":\"The date the user pool description was last modified.
\"\ },\ \"CreationDate\":{\ \"shape\":\"DateType\",\ \"documentation\":\"The date the user pool description was created.
\"\ }\ },\ \"documentation\":\"A user pool description.
\"\ },\ \"UserPoolIdType\":{\ \"type\":\"string\",\ \"max\":55,\ \"min\":1,\ \"pattern\":\"[\\\\w-]+_[0-9a-zA-Z]+\"\ },\ \"UserPoolListType\":{\ \"type\":\"list\",\ \"member\":{\"shape\":\"UserPoolDescriptionType\"}\ },\ \"UserPoolMfaType\":{\ \"type\":\"string\",\ \"enum\":[\ \"OFF\",\ \"ON\",\ \"OPTIONAL\"\ ]\ },\ \"UserPoolNameType\":{\ \"type\":\"string\",\ \"max\":128,\ \"min\":1,\ \"pattern\":\"[\\\\w\\\\s+=,.@-]+\"\ },\ \"UserPoolPolicyType\":{\ \"type\":\"structure\",\ \"members\":{\ \"PasswordPolicy\":{\ \"shape\":\"PasswordPolicyType\",\ \"documentation\":\"The password policy.
\"\ }\ },\ \"documentation\":\"The policy associated with a user pool.
\"\ },\ \"UserPoolTaggingException\":{\ \"type\":\"structure\",\ \"members\":{\ \"message\":{\"shape\":\"MessageType\"}\ },\ \"documentation\":\"This exception is thrown when a user pool tag can't be set or updated.
\",\ \"exception\":true\ },\ \"UserPoolTagsListType\":{\ \"type\":\"list\",\ \"member\":{\"shape\":\"TagKeysType\"}\ },\ \"UserPoolTagsType\":{\ \"type\":\"map\",\ \"key\":{\"shape\":\"TagKeysType\"},\ \"value\":{\"shape\":\"TagValueType\"}\ },\ \"UserPoolType\":{\ \"type\":\"structure\",\ \"members\":{\ \"Id\":{\ \"shape\":\"UserPoolIdType\",\ \"documentation\":\"The ID of the user pool.
\"\ },\ \"Name\":{\ \"shape\":\"UserPoolNameType\",\ \"documentation\":\"The name of the user pool.
\"\ },\ \"Policies\":{\ \"shape\":\"UserPoolPolicyType\",\ \"documentation\":\"The policies associated with the user pool.
\"\ },\ \"DeletionProtection\":{\ \"shape\":\"DeletionProtectionType\",\ \"documentation\":\"When active, DeletionProtection
prevents accidental deletion of your user pool. Before you can delete a user pool that you have protected against deletion, you must deactivate this feature.
When you try to delete a protected user pool in a DeleteUserPool
API request, Amazon Cognito returns an InvalidParameterException
error. To delete a protected user pool, send a new DeleteUserPool
request after you deactivate deletion protection in an UpdateUserPool
API request.
The Lambda triggers associated with the user pool.
\"\ },\ \"Status\":{\ \"shape\":\"StatusType\",\ \"documentation\":\"The status of a user pool.
\"\ },\ \"LastModifiedDate\":{\ \"shape\":\"DateType\",\ \"documentation\":\"The date the user pool was last modified.
\"\ },\ \"CreationDate\":{\ \"shape\":\"DateType\",\ \"documentation\":\"The date the user pool was created.
\"\ },\ \"SchemaAttributes\":{\ \"shape\":\"SchemaAttributesListType\",\ \"documentation\":\"A container with the schema attributes of a user pool.
\"\ },\ \"AutoVerifiedAttributes\":{\ \"shape\":\"VerifiedAttributesListType\",\ \"documentation\":\"The attributes that are auto-verified in a user pool.
\"\ },\ \"AliasAttributes\":{\ \"shape\":\"AliasAttributesListType\",\ \"documentation\":\"The attributes that are aliased in a user pool.
\"\ },\ \"UsernameAttributes\":{\ \"shape\":\"UsernameAttributesListType\",\ \"documentation\":\"Specifies whether a user can use an email address or phone number as a username when they sign up.
\"\ },\ \"SmsVerificationMessage\":{\ \"shape\":\"SmsVerificationMessageType\",\ \"documentation\":\"This parameter is no longer used. See VerificationMessageTemplateType.
\"\ },\ \"EmailVerificationMessage\":{\ \"shape\":\"EmailVerificationMessageType\",\ \"documentation\":\"This parameter is no longer used. See VerificationMessageTemplateType.
\"\ },\ \"EmailVerificationSubject\":{\ \"shape\":\"EmailVerificationSubjectType\",\ \"documentation\":\"This parameter is no longer used. See VerificationMessageTemplateType.
\"\ },\ \"VerificationMessageTemplate\":{\ \"shape\":\"VerificationMessageTemplateType\",\ \"documentation\":\"The template for verification messages.
\"\ },\ \"SmsAuthenticationMessage\":{\ \"shape\":\"SmsVerificationMessageType\",\ \"documentation\":\"The contents of the SMS authentication message.
\"\ },\ \"UserAttributeUpdateSettings\":{\ \"shape\":\"UserAttributeUpdateSettingsType\",\ \"documentation\":\"The settings for updates to user attributes. These settings include the property AttributesRequireVerificationBeforeUpdate
, a user-pool setting that tells Amazon Cognito how to handle changes to the value of your users' email address and phone number attributes. For more information, see Verifying updates to email addresses and phone numbers.
Can be one of the following values:
OFF
- MFA tokens aren't required and can't be specified during user registration.
ON
- MFA tokens are required for all user registrations. You can only specify required when you're initially creating a user pool.
OPTIONAL
- Users have the option when registering to create an MFA token.
The device-remembering configuration for a user pool. A null value indicates that you have deactivated device remembering in your user pool.
When you provide a value for any DeviceConfiguration
field, you activate the Amazon Cognito device-remembering feature.
A number estimating the size of the user pool.
\"\ },\ \"EmailConfiguration\":{\ \"shape\":\"EmailConfigurationType\",\ \"documentation\":\"The email configuration of your user pool. The email configuration type sets your preferred sending method, Amazon Web Services Region, and sender for messages tfrom your user pool.
\"\ },\ \"SmsConfiguration\":{\ \"shape\":\"SmsConfigurationType\",\ \"documentation\":\"The SMS configuration with the settings that your Amazon Cognito user pool must use to send an SMS message from your Amazon Web Services account through Amazon Simple Notification Service. To send SMS messages with Amazon SNS in the Amazon Web Services Region that you want, the Amazon Cognito user pool uses an Identity and Access Management (IAM) role in your Amazon Web Services account.
\"\ },\ \"UserPoolTags\":{\ \"shape\":\"UserPoolTagsType\",\ \"documentation\":\"The tags that are assigned to the user pool. A tag is a label that you can apply to user pools to categorize and manage them in different ways, such as by purpose, owner, environment, or other criteria.
\"\ },\ \"SmsConfigurationFailure\":{\ \"shape\":\"StringType\",\ \"documentation\":\"The reason why the SMS configuration can't send the messages to your users.
This message might include comma-separated values to describe why your SMS configuration can't send messages to user pool end users.
The Identity and Access Management role that Amazon Cognito uses to send SMS messages isn't properly configured. For more information, see SmsConfigurationType.
The Amazon Web Services account is in the SNS SMS Sandbox and messages will only reach verified end users. This parameter wonât get populated with SNSSandbox if the IAM user creating the user pool doesnât have SNS permissions. To learn how to move your Amazon Web Services account out of the sandbox, see Moving out of the SMS sandbox.
Deprecated. Review error codes from API requests with EventSource:cognito-idp.amazonaws.com
in CloudTrail for information about problems with user pool email configuration.
The domain prefix, if the user pool has a domain associated with it.
\"\ },\ \"CustomDomain\":{\ \"shape\":\"DomainType\",\ \"documentation\":\"A custom domain name that you provide to Amazon Cognito. This parameter applies only if you use a custom domain to host the sign-up and sign-in pages for your application. An example of a custom domain name might be auth.example.com
.
For more information about adding a custom domain to your user pool, see Using Your Own Domain for the Hosted UI.
\"\ },\ \"AdminCreateUserConfig\":{\ \"shape\":\"AdminCreateUserConfigType\",\ \"documentation\":\"The configuration for AdminCreateUser
requests.
The user pool add-ons.
\"\ },\ \"UsernameConfiguration\":{\ \"shape\":\"UsernameConfigurationType\",\ \"documentation\":\"Case sensitivity of the username input for the selected sign-in option. For example, when case sensitivity is set to False
, users can sign in using either \\\"username\\\" or \\\"Username\\\". This configuration is immutable once it has been set. For more information, see UsernameConfigurationType.
The Amazon Resource Name (ARN) for the user pool.
\"\ },\ \"AccountRecoverySetting\":{\ \"shape\":\"AccountRecoverySettingType\",\ \"documentation\":\"The available verified method a user can use to recover their password when they call ForgotPassword
. You can use this setting to define a preferred method when a user has more than one method available. With this setting, SMS doesn't qualify for a valid password recovery mechanism if the user also has SMS multi-factor authentication (MFA) activated. In the absence of this setting, Amazon Cognito uses the legacy behavior to determine the recovery method where SMS is preferred through email.
A container for information about the user pool.
\"\ },\ \"UserStatusType\":{\ \"type\":\"string\",\ \"enum\":[\ \"UNCONFIRMED\",\ \"CONFIRMED\",\ \"ARCHIVED\",\ \"COMPROMISED\",\ \"UNKNOWN\",\ \"RESET_REQUIRED\",\ \"FORCE_CHANGE_PASSWORD\"\ ]\ },\ \"UserType\":{\ \"type\":\"structure\",\ \"members\":{\ \"Username\":{\ \"shape\":\"UsernameType\",\ \"documentation\":\"The user name of the user you want to describe.
\"\ },\ \"Attributes\":{\ \"shape\":\"AttributeListType\",\ \"documentation\":\"A container with information about the user type attributes.
\"\ },\ \"UserCreateDate\":{\ \"shape\":\"DateType\",\ \"documentation\":\"The creation date of the user.
\"\ },\ \"UserLastModifiedDate\":{\ \"shape\":\"DateType\",\ \"documentation\":\"The last modified date of the user.
\"\ },\ \"Enabled\":{\ \"shape\":\"BooleanType\",\ \"documentation\":\"Specifies whether the user is enabled.
\"\ },\ \"UserStatus\":{\ \"shape\":\"UserStatusType\",\ \"documentation\":\"The user status. This can be one of the following:
UNCONFIRMED - User has been created but not confirmed.
CONFIRMED - User has been confirmed.
EXTERNAL_PROVIDER - User signed in with a third-party IdP.
ARCHIVED - User is no longer active.
UNKNOWN - User status isn't known.
RESET_REQUIRED - User is confirmed, but the user must request a code and reset their password before they can sign in.
FORCE_CHANGE_PASSWORD - The user is confirmed and the user can sign in using a temporary password, but on first sign-in, the user must change their password to a new value before doing anything else.
The MFA options for the user.
\"\ }\ },\ \"documentation\":\"A user profile in a Amazon Cognito user pool.
\"\ },\ \"UsernameAttributeType\":{\ \"type\":\"string\",\ \"enum\":[\ \"phone_number\",\ \"email\"\ ]\ },\ \"UsernameAttributesListType\":{\ \"type\":\"list\",\ \"member\":{\"shape\":\"UsernameAttributeType\"}\ },\ \"UsernameConfigurationType\":{\ \"type\":\"structure\",\ \"required\":[\"CaseSensitive\"],\ \"members\":{\ \"CaseSensitive\":{\ \"shape\":\"WrappedBooleanType\",\ \"documentation\":\"Specifies whether user name case sensitivity will be applied for all users in the user pool through Amazon Cognito APIs.
Valid values include:
Enables case sensitivity for all username input. When this option is set to True
, users must sign in using the exact capitalization of their given username, such as âUserNameâ. This is the default value.
Enables case insensitivity for all username input. For example, when this option is set to False
, users can sign in using either \\\"username\\\" or \\\"Username\\\". This option also enables both preferred_username
and email
alias to be case insensitive, in addition to the username
attribute.
The username configuration type.
\"\ },\ \"UsernameExistsException\":{\ \"type\":\"structure\",\ \"members\":{\ \"message\":{\ \"shape\":\"MessageType\",\ \"documentation\":\"The message returned when Amazon Cognito throws a user name exists exception.
\"\ }\ },\ \"documentation\":\"This exception is thrown when Amazon Cognito encounters a user name that already exists in the user pool.
\",\ \"exception\":true\ },\ \"UsernameType\":{\ \"type\":\"string\",\ \"max\":128,\ \"min\":1,\ \"pattern\":\"[\\\\p{L}\\\\p{M}\\\\p{S}\\\\p{N}\\\\p{P}]+\",\ \"sensitive\":true\ },\ \"UsersListType\":{\ \"type\":\"list\",\ \"member\":{\"shape\":\"UserType\"}\ },\ \"VerificationMessageTemplateType\":{\ \"type\":\"structure\",\ \"members\":{\ \"SmsMessage\":{\ \"shape\":\"SmsVerificationMessageType\",\ \"documentation\":\"The template for SMS messages that Amazon Cognito sends to your users.
\"\ },\ \"EmailMessage\":{\ \"shape\":\"EmailVerificationMessageType\",\ \"documentation\":\"The template for email messages that Amazon Cognito sends to your users. You can set an EmailMessage
template only if the value of EmailSendingAccount is DEVELOPER
. When your EmailSendingAccount is DEVELOPER
, your user pool sends email messages with your own Amazon SES configuration.
The subject line for the email message template. You can set an EmailSubject
template only if the value of EmailSendingAccount is DEVELOPER
. When your EmailSendingAccount is DEVELOPER
, your user pool sends email messages with your own Amazon SES configuration.
The email message template for sending a confirmation link to the user. You can set an EmailMessageByLink
template only if the value of EmailSendingAccount is DEVELOPER
. When your EmailSendingAccount is DEVELOPER
, your user pool sends email messages with your own Amazon SES configuration.
The subject line for the email message template for sending a confirmation link to the user. You can set an EmailSubjectByLink
template only if the value of EmailSendingAccount is DEVELOPER
. When your EmailSendingAccount is DEVELOPER
, your user pool sends email messages with your own Amazon SES configuration.
The default email option.
\"\ }\ },\ \"documentation\":\"The template for verification messages.
\"\ },\ \"VerifiedAttributeType\":{\ \"type\":\"string\",\ \"enum\":[\ \"phone_number\",\ \"email\"\ ]\ },\ \"VerifiedAttributesListType\":{\ \"type\":\"list\",\ \"member\":{\"shape\":\"VerifiedAttributeType\"}\ },\ \"VerifySoftwareTokenRequest\":{\ \"type\":\"structure\",\ \"required\":[\"UserCode\"],\ \"members\":{\ \"AccessToken\":{\ \"shape\":\"TokenModelType\",\ \"documentation\":\"A valid access token that Amazon Cognito issued to the user whose software token you want to verify.
\"\ },\ \"Session\":{\ \"shape\":\"SessionType\",\ \"documentation\":\"The session that should be passed both ways in challenge-response calls to the service.
\"\ },\ \"UserCode\":{\ \"shape\":\"SoftwareTokenMFAUserCodeType\",\ \"documentation\":\"The one- time password computed using the secret code returned by AssociateSoftwareToken.
\"\ },\ \"FriendlyDeviceName\":{\ \"shape\":\"StringType\",\ \"documentation\":\"The friendly device name.
\"\ }\ }\ },\ \"VerifySoftwareTokenResponse\":{\ \"type\":\"structure\",\ \"members\":{\ \"Status\":{\ \"shape\":\"VerifySoftwareTokenResponseType\",\ \"documentation\":\"The status of the verify software token.
\"\ },\ \"Session\":{\ \"shape\":\"SessionType\",\ \"documentation\":\"The session that should be passed both ways in challenge-response calls to the service.
\"\ }\ }\ },\ \"VerifySoftwareTokenResponseType\":{\ \"type\":\"string\",\ \"enum\":[\ \"SUCCESS\",\ \"ERROR\"\ ]\ },\ \"VerifyUserAttributeRequest\":{\ \"type\":\"structure\",\ \"required\":[\ \"AccessToken\",\ \"AttributeName\",\ \"Code\"\ ],\ \"members\":{\ \"AccessToken\":{\ \"shape\":\"TokenModelType\",\ \"documentation\":\"A valid access token that Amazon Cognito issued to the user whose user attributes you want to verify.
\"\ },\ \"AttributeName\":{\ \"shape\":\"AttributeNameType\",\ \"documentation\":\"The attribute name in the request to verify user attributes.
\"\ },\ \"Code\":{\ \"shape\":\"ConfirmationCodeType\",\ \"documentation\":\"The verification code in the request to verify user attributes.
\"\ }\ },\ \"documentation\":\"Represents the request to verify user attributes.
\"\ },\ \"VerifyUserAttributeResponse\":{\ \"type\":\"structure\",\ \"members\":{\ },\ \"documentation\":\"A container representing the response from the server from the request to verify user attributes.
\"\ },\ \"WrappedBooleanType\":{\"type\":\"boolean\"}\ },\ \"documentation\":\"Using the Amazon Cognito user pools API, you can create a user pool to manage directories and users. You can authenticate a user to obtain tokens related to user identity and access policies.
This API reference provides information about user pools in Amazon Cognito user pools.
For more information, see the Amazon Cognito Documentation.
\"\ }\ "; } @end