adminRespondToAuthChallenge method
Some API operations in a user pool generate a challenge, like a prompt for
an MFA code, for device authentication that bypasses MFA, or for a custom
authentication challenge. An AdminRespondToAuthChallenge API
request provides the answer to that challenge, like a code or a secure
remote password (SRP). The parameters of a response to an authentication
challenge vary with the type of challenge.
For more information about custom authentication challenges, see Custom authentication challenge Lambda triggers.
If you have never used SMS text messages with Amazon Cognito or any other Amazon Web Services 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.
Learn more
- Signing Amazon Web Services API Requests
- Using the Amazon Cognito user pools API and user pool endpoints
May throw AliasExistsException.
May throw CodeMismatchException.
May throw ExpiredCodeException.
May throw InternalErrorException.
May throw InvalidEmailRoleAccessPolicyException.
May throw InvalidLambdaResponseException.
May throw InvalidParameterException.
May throw InvalidPasswordException.
May throw InvalidSmsRoleAccessPolicyException.
May throw InvalidSmsRoleTrustRelationshipException.
May throw InvalidUserPoolConfigurationException.
May throw MFAMethodNotFoundException.
May throw NotAuthorizedException.
May throw OperationNotEnabledException.
May throw PasswordHistoryPolicyViolationException.
May throw PasswordResetRequiredException.
May throw ResourceNotFoundException.
May throw SoftwareTokenMFANotFoundException.
May throw TooManyRequestsException.
May throw UnexpectedLambdaException.
May throw UserLambdaValidationException.
May throw UserNotConfirmedException.
May throw UserNotFoundException.
Parameter challengeName :
The name of the challenge that you are responding to.
Possible challenges include the following:
-
WEB_AUTHN: Respond to the challenge with the results of a successful authentication with a WebAuthn authenticator, or passkey, asCREDENTIAL. Examples of WebAuthn authenticators include biometric devices and security keys. -
PASSWORD: Respond with the user's password asPASSWORD. -
PASSWORD_SRP: Respond with the initial SRP secret asSRP_A. -
SELECT_CHALLENGE: Respond with a challenge selection asANSWER. It must be one of the challenge types in theAvailableChallengesresponse parameter. Add the parameters of the selected challenge, for exampleUSERNAMEandSMS_OTP. -
SMS_MFA: Respond with the code that your user pool delivered in an SMS message, asSMS_MFA_CODE -
EMAIL_MFA: Respond with the code that your user pool delivered in an email message, asEMAIL_MFA_CODE -
EMAIL_OTP: Respond with the code that your user pool delivered in an email message, asEMAIL_OTP_CODE. -
SMS_OTP: Respond with the code that your user pool delivered in an SMS message, asSMS_OTP_CODE. -
PASSWORD_VERIFIER: Respond with the second stage of SRP secrets asPASSWORD_CLAIM_SIGNATURE,PASSWORD_CLAIM_SECRET_BLOCK, andTIMESTAMP. -
CUSTOM_CHALLENGE: This is returned if your custom authentication flow determines that the user should pass another challenge before tokens are issued. The parameters of the challenge are determined by your Lambda function and issued in theChallengeParametersof a challenge response. -
DEVICE_SRP_AUTH: Respond with the initial parameters of device SRP authentication. For more information, see Signing in with a device. -
DEVICE_PASSWORD_VERIFIER: Respond withPASSWORD_CLAIM_SIGNATURE,PASSWORD_CLAIM_SECRET_BLOCK, andTIMESTAMPafter client-side SRP calculations. For more information, see Signing in with a device. -
NEW_PASSWORD_REQUIRED: For users who are required to change their passwords after successful first login. Respond to this challenge withNEW_PASSWORDand any required attributes that Amazon Cognito returned in therequiredAttributesparameter. You can also set values for attributes that aren't required by your user pool and that your app client can write.Amazon Cognito only returns this challenge for users who have temporary passwords. When you create passwordless users, you must provide values for all required 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 parametersMFAS_CAN_SETUPvalue.To set up time-based one-time password (TOTP) MFA, use the session returned in this challenge from
InitiateAuthorAdminInitiateAuthas an input toAssociateSoftwareToken. Then, use the session returned byVerifySoftwareTokenas an input toRespondToAuthChallengeorAdminRespondToAuthChallengewith challenge nameMFA_SETUPto complete sign-in.To set up SMS or email MFA, collect a
phone_numberoremailattribute for the user. Then restart the authentication flow with anInitiateAuthorAdminInitiateAuthrequest.
Parameter clientId :
The ID of the app client where you initiated sign-in.
Parameter userPoolId :
The ID of the user pool where you want to respond to an authentication
challenge.
Parameter analyticsMetadata :
Information that supports analytics outcomes with Amazon Pinpoint,
including the user's endpoint ID. The endpoint ID is a destination for
Amazon Pinpoint push notifications, for example a device identifier, email
address, or phone number.
Parameter challengeResponses :
The responses to the challenge that you received in the previous request.
Each challenge has its own required response parameters. The following
examples are partial JSON request bodies that highlight challenge-response
parameters.
- SELECT_CHALLENGE
-
"ChallengeName": "SELECT_CHALLENGE", "ChallengeResponses": { "USERNAME": "[username]", "ANSWER": "[Challenge name]"}Available challenges are
PASSWORD,PASSWORD_SRP,EMAIL_OTP,SMS_OTP, andWEB_AUTHN.Complete authentication in the
SELECT_CHALLENGEresponse forPASSWORD,PASSWORD_SRP, andWEB_AUTHN:-
"ChallengeName": "SELECT_CHALLENGE", "ChallengeResponses": { "ANSWER": "WEB_AUTHN", "USERNAME": "\[username\]", "CREDENTIAL": "\[AuthenticationResponseJSON\]"} -
"ChallengeName": "SELECT_CHALLENGE", "ChallengeResponses": { "ANSWER": "PASSWORD", "USERNAME": "\[username\]", "PASSWORD": "\[password\]"} -
"ChallengeName": "SELECT_CHALLENGE", "ChallengeResponses": { "ANSWER": "PASSWORD_SRP", "USERNAME": "\[username\]", "SRP_A": "\[SRP_A\]"}
SMS_OTPandEMAIL_OTP, respond with the username and answer. Your user pool will send a code for the user to submit in the next challenge response.-
"ChallengeName": "SELECT_CHALLENGE", "ChallengeResponses": { "ANSWER": "SMS_OTP", "USERNAME": "\[username\]"} -
"ChallengeName": "SELECT_CHALLENGE", "ChallengeResponses": { "ANSWER": "EMAIL_OTP", "USERNAME": "\[username\]"}
-
- WEB_AUTHN
-
"ChallengeName": "WEB_AUTHN", "ChallengeResponses": { "USERNAME": "\[username\]", "CREDENTIAL": "\[AuthenticationResponseJSON\]"} - PASSWORD
-
"ChallengeName": "PASSWORD", "ChallengeResponses": { "USERNAME": "\[username\]", "PASSWORD": "\[password\]"} - PASSWORD_SRP
-
"ChallengeName": "PASSWORD_SRP", "ChallengeResponses": { "USERNAME": "\[username\]", "SRP_A": "\[SRP_A\]"} - SMS_OTP
-
"ChallengeName": "SMS_OTP", "ChallengeResponses": {"SMS_OTP_CODE": "\[code\]", "USERNAME": "\[username\]"} - EMAIL_OTP
-
"ChallengeName": "EMAIL_OTP", "ChallengeResponses": {"EMAIL_OTP_CODE": "\[code\]", "USERNAME": "\[username\]"} - SMS_MFA
-
"ChallengeName": "SMS_MFA", "ChallengeResponses": {"SMS_MFA_CODE": "\[code\]", "USERNAME": "\[username\]"} - PASSWORD_VERIFIER
-
This challenge response is part of the SRP flow. Amazon Cognito requires
that your application respond to this challenge within a few seconds. When
the response time exceeds this period, your user pool returns a
NotAuthorizedExceptionerror."ChallengeName": "PASSWORD_VERIFIER", "ChallengeResponses": {"PASSWORD_CLAIM_SIGNATURE": "[claim_signature]", "PASSWORD_CLAIM_SECRET_BLOCK": "[secret_block]", "TIMESTAMP": [timestamp], "USERNAME": "[username]"} - CUSTOM_CHALLENGE
-
"ChallengeName": "CUSTOM_CHALLENGE", "ChallengeResponses": {"USERNAME": "\[username\]", "ANSWER": "\[challenge_answer\]"} - NEW_PASSWORD_REQUIRED
-
"ChallengeName": "NEW_PASSWORD_REQUIRED", "ChallengeResponses": {"NEW_PASSWORD": "\[new_password\]", "USERNAME": "\[username\]"}To set any required attributes that
InitiateAuthreturned in anrequiredAttributesparameter, add"userAttributes.[attribute_name]": "[attribute_value]". This parameter can also set values for writable attributes that aren't required by your user pool. - SOFTWARE_TOKEN_MFA
-
"ChallengeName": "SOFTWARE_TOKEN_MFA", "ChallengeResponses": {"USERNAME": "[username]", "SOFTWARE_TOKEN_MFA_CODE": [authenticator_code]} - DEVICE_SRP_AUTH
-
"ChallengeName": "DEVICE_SRP_AUTH", "ChallengeResponses": {"USERNAME": "\[username\]", "DEVICE_KEY": "\[device_key\]", "SRP_A": "\[srp_a\]"} - DEVICE_PASSWORD_VERIFIER
-
"ChallengeName": "DEVICE_PASSWORD_VERIFIER", "ChallengeResponses": {"DEVICE_KEY": "\[device_key\]", "PASSWORD_CLAIM_SIGNATURE": "\[claim_signature\]", "PASSWORD_CLAIM_SECRET_BLOCK": "\[secret_block\]", "TIMESTAMP": \[timestamp\], "USERNAME": "\[username\]"} - MFA_SETUP
-
"ChallengeName": "MFA_SETUP", "ChallengeResponses": {"USERNAME": "\[username\]"}, "SESSION": "\[Session ID from VerifySoftwareToken\]" - SELECT_MFA_TYPE
-
"ChallengeName": "SELECT_MFA_TYPE", "ChallengeResponses": {"USERNAME": "\[username\]", "ANSWER": "\[SMS_MFA|EMAIL_MFA|SOFTWARE_TOKEN_MFA\]"}
SECRET_HASH, see Computing
secret hash values. For information about DEVICE_KEY, see
Working
with user devices in your user pool.
Parameter clientMetadata :
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 Amazon Cognito invokes any of these functions, it passes a JSON
payload, which the function receives as input. This payload contains a
clientMetadata attribute that provides the data that you
assigned to the ClientMetadata parameter in your request. In your function
code, you can process the clientMetadata value to enhance
your workflow for your specific needs.
To review the Lambda trigger types that Amazon Cognito invokes at runtime with API requests, see Connecting API actions to Lambda triggers in the Amazon Cognito Developer Guide.
-
Store the
ClientMetadatavalue. 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, theClientMetadataparameter serves no purpose. -
Validate the
ClientMetadatavalue. -
Encrypt the
ClientMetadatavalue. Don't send sensitive information in this parameter.
Parameter contextData :
Contextual data about your user session like the device fingerprint, IP
address, or location. Amazon Cognito threat protection 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.
For more information, see Collecting data for threat protection in applications.
Parameter session :
The session identifier that maintains the state of authentication requests
and challenge responses. If an AdminInitiateAuth or
AdminRespondToAuthChallenge API request results in a
determination that your application must pass another challenge, Amazon
Cognito returns a session with other challenge parameters. Send this
session identifier, unmodified, to the next
AdminRespondToAuthChallenge request.
Implementation
Future<AdminRespondToAuthChallengeResponse> adminRespondToAuthChallenge({
required ChallengeNameType challengeName,
required String clientId,
required String userPoolId,
AnalyticsMetadataType? analyticsMetadata,
Map<String, String>? challengeResponses,
Map<String, String>? clientMetadata,
ContextDataType? contextData,
String? session,
}) async {
final headers = <String, String>{
'Content-Type': 'application/x-amz-json-1.1',
'X-Amz-Target':
'AWSCognitoIdentityProviderService.AdminRespondToAuthChallenge'
};
final jsonResponse = await _protocol.send(
method: 'POST',
requestUri: '/',
exceptionFnMap: _exceptionFns,
// TODO queryParams
headers: headers,
payload: {
'ChallengeName': challengeName.value,
'ClientId': clientId,
'UserPoolId': userPoolId,
if (analyticsMetadata != null) 'AnalyticsMetadata': analyticsMetadata,
if (challengeResponses != null)
'ChallengeResponses': challengeResponses,
if (clientMetadata != null) 'ClientMetadata': clientMetadata,
if (contextData != null) 'ContextData': contextData,
if (session != null) 'Session': session,
},
);
return AdminRespondToAuthChallengeResponse.fromJson(jsonResponse.body);
}