@Generated(value="com.amazonaws:aws-java-sdk-code-generator") public class RespondToAuthChallengeRequest extends AmazonWebServiceRequest implements Serializable, Cloneable
The request to respond to an authentication challenge.
NOOP
Constructor and Description |
---|
RespondToAuthChallengeRequest() |
Modifier and Type | Method and Description |
---|---|
RespondToAuthChallengeRequest |
addChallengeResponsesEntry(String key,
String value)
Add a single ChallengeResponses entry
|
RespondToAuthChallengeRequest |
addClientMetadataEntry(String key,
String value)
Add a single ClientMetadata entry
|
RespondToAuthChallengeRequest |
clearChallengeResponsesEntries()
Removes all the entries added into ChallengeResponses.
|
RespondToAuthChallengeRequest |
clearClientMetadataEntries()
Removes all the entries added into ClientMetadata.
|
RespondToAuthChallengeRequest |
clone()
Creates a shallow clone of this object for all fields except the handler context.
|
boolean |
equals(Object obj) |
AnalyticsMetadataType |
getAnalyticsMetadata()
The Amazon Pinpoint analytics metadata that contributes to your metrics for
RespondToAuthChallenge
calls. |
String |
getChallengeName()
The challenge name.
|
Map<String,String> |
getChallengeResponses()
The responses to the challenge that you received in the previous request.
|
String |
getClientId()
The app client ID.
|
Map<String,String> |
getClientMetadata()
A map of custom key-value pairs that you can provide as input for any custom workflows that this action triggers.
|
String |
getSession()
The session that should be passed both ways in challenge-response calls to the service.
|
UserContextDataType |
getUserContextData()
Contextual data about your user session, such as the device fingerprint, IP address, or location.
|
int |
hashCode() |
void |
setAnalyticsMetadata(AnalyticsMetadataType analyticsMetadata)
The Amazon Pinpoint analytics metadata that contributes to your metrics for
RespondToAuthChallenge
calls. |
void |
setChallengeName(ChallengeNameType challengeName)
The challenge name.
|
void |
setChallengeName(String challengeName)
The challenge name.
|
void |
setChallengeResponses(Map<String,String> challengeResponses)
The responses to the challenge that you received in the previous request.
|
void |
setClientId(String clientId)
The app client ID.
|
void |
setClientMetadata(Map<String,String> clientMetadata)
A map of custom key-value pairs that you can provide as input for any custom workflows that this action triggers.
|
void |
setSession(String session)
The session that should be passed both ways in challenge-response calls to the service.
|
void |
setUserContextData(UserContextDataType userContextData)
Contextual data about your user session, such as the device fingerprint, IP address, or location.
|
String |
toString()
Returns a string representation of this object.
|
RespondToAuthChallengeRequest |
withAnalyticsMetadata(AnalyticsMetadataType analyticsMetadata)
The Amazon Pinpoint analytics metadata that contributes to your metrics for
RespondToAuthChallenge
calls. |
RespondToAuthChallengeRequest |
withChallengeName(ChallengeNameType challengeName)
The challenge name.
|
RespondToAuthChallengeRequest |
withChallengeName(String challengeName)
The challenge name.
|
RespondToAuthChallengeRequest |
withChallengeResponses(Map<String,String> challengeResponses)
The responses to the challenge that you received in the previous request.
|
RespondToAuthChallengeRequest |
withClientId(String clientId)
The app client ID.
|
RespondToAuthChallengeRequest |
withClientMetadata(Map<String,String> clientMetadata)
A map of custom key-value pairs that you can provide as input for any custom workflows that this action triggers.
|
RespondToAuthChallengeRequest |
withSession(String session)
The session that should be passed both ways in challenge-response calls to the service.
|
RespondToAuthChallengeRequest |
withUserContextData(UserContextDataType userContextData)
Contextual data about your user session, such as the device fingerprint, IP address, or location.
|
addHandlerContext, getCloneRoot, getCloneSource, getCustomQueryParameters, getCustomRequestHeaders, getGeneralProgressListener, getHandlerContext, getReadLimit, getRequestClientOptions, getRequestCredentials, getRequestCredentialsProvider, getRequestMetricCollector, getSdkClientExecutionTimeout, getSdkRequestTimeout, putCustomQueryParameter, putCustomRequestHeader, setGeneralProgressListener, setRequestCredentials, setRequestCredentialsProvider, setRequestMetricCollector, setSdkClientExecutionTimeout, setSdkRequestTimeout, withGeneralProgressListener, withRequestCredentialsProvider, withRequestMetricCollector, withSdkClientExecutionTimeout, withSdkRequestTimeout
public void setClientId(String clientId)
The app client ID.
clientId
- The app client ID.public String getClientId()
The app client ID.
public RespondToAuthChallengeRequest withClientId(String clientId)
The app client ID.
clientId
- The app client ID.public void setChallengeName(String challengeName)
The challenge name. For more information, see InitiateAuth.
ADMIN_NO_SRP_AUTH
isn't a valid value.
challengeName
- The challenge name. For more information, see InitiateAuth.
ADMIN_NO_SRP_AUTH
isn't a valid value.
ChallengeNameType
public String getChallengeName()
The challenge name. For more information, see InitiateAuth.
ADMIN_NO_SRP_AUTH
isn't a valid value.
ADMIN_NO_SRP_AUTH
isn't a valid value.
ChallengeNameType
public RespondToAuthChallengeRequest withChallengeName(String challengeName)
The challenge name. For more information, see InitiateAuth.
ADMIN_NO_SRP_AUTH
isn't a valid value.
challengeName
- The challenge name. For more information, see InitiateAuth.
ADMIN_NO_SRP_AUTH
isn't a valid value.
ChallengeNameType
public void setChallengeName(ChallengeNameType challengeName)
The challenge name. For more information, see InitiateAuth.
ADMIN_NO_SRP_AUTH
isn't a valid value.
challengeName
- The challenge name. For more information, see InitiateAuth.
ADMIN_NO_SRP_AUTH
isn't a valid value.
ChallengeNameType
public RespondToAuthChallengeRequest withChallengeName(ChallengeNameType challengeName)
The challenge name. For more information, see InitiateAuth.
ADMIN_NO_SRP_AUTH
isn't a valid value.
challengeName
- The challenge name. For more information, see InitiateAuth.
ADMIN_NO_SRP_AUTH
isn't a valid value.
ChallengeNameType
public void setSession(String session)
The session that should be passed both ways in challenge-response calls to the service. If
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.
session
- The session that should be passed both ways in challenge-response calls to the service. If
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.public String getSession()
The session that should be passed both ways in challenge-response calls to the service. If
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.
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.public RespondToAuthChallengeRequest withSession(String session)
The session that should be passed both ways in challenge-response calls to the service. If
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.
session
- The session that should be passed both ways in challenge-response calls to the service. If
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.public Map<String,String> getChallengeResponses()
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.
You must provide a SECRET_HASH parameter in all challenge responses to an app client that has a client secret.
"ChallengeName": "SMS_MFA", "ChallengeResponses": {"SMS_MFA_CODE": "[SMS_code]", "USERNAME": "[username]"}
"ChallengeName": "PASSWORD_VERIFIER", "ChallengeResponses": {"PASSWORD_CLAIM_SIGNATURE": "[claim_signature]", "PASSWORD_CLAIM_SECRET_BLOCK": "[secret_block]", "TIMESTAMP": [timestamp], "USERNAME": "[username]"}
Add "DEVICE_KEY"
when you sign in with a remembered device.
"ChallengeName": "CUSTOM_CHALLENGE", "ChallengeResponses": {"USERNAME": "[username]", "ANSWER": "[challenge_answer]"}
Add "DEVICE_KEY"
when you sign in with a remembered device.
"ChallengeName": "NEW_PASSWORD_REQUIRED", "ChallengeResponses": {"NEW_PASSWORD": "[new_password]", "USERNAME": "[username]"}
To set any required attributes that InitiateAuth
returned in an requiredAttributes
parameter, add "userAttributes.[attribute_name]": "[attribute_value]"
. This parameter can also set
values for writable attributes that aren't required by your user pool.
In a 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.
"ChallengeName": "SOFTWARE_TOKEN_MFA", "ChallengeResponses": {"USERNAME": "[username]", "SOFTWARE_TOKEN_MFA_CODE": [authenticator_code]}
"ChallengeName": "DEVICE_SRP_AUTH", "ChallengeResponses": {"USERNAME": "[username]", "DEVICE_KEY": "[device_key]", "SRP_A": "[srp_a]"}
"ChallengeName": "DEVICE_PASSWORD_VERIFIER", "ChallengeResponses": {"DEVICE_KEY": "[device_key]", "PASSWORD_CLAIM_SIGNATURE": "[claim_signature]", "PASSWORD_CLAIM_SECRET_BLOCK": "[secret_block]", "TIMESTAMP": [timestamp], "USERNAME": "[username]"}
"ChallengeName": "MFA_SETUP", "ChallengeResponses": {"USERNAME": "[username]"}, "SESSION": "[Session ID from VerifySoftwareToken]"
"ChallengeName": "SELECT_MFA_TYPE", "ChallengeResponses": {"USERNAME": "[username]", "ANSWER": "[SMS_MFA or SOFTWARE_TOKEN_MFA]"}
For more information about SECRET_HASH
, see Computing secret hash values. For information about DEVICE_KEY
, see Working with user devices in your user pool.
You must provide a SECRET_HASH parameter in all challenge responses to an app client that has a client secret.
"ChallengeName": "SMS_MFA", "ChallengeResponses": {"SMS_MFA_CODE": "[SMS_code]", "USERNAME": "[username]"}
"ChallengeName": "PASSWORD_VERIFIER", "ChallengeResponses": {"PASSWORD_CLAIM_SIGNATURE": "[claim_signature]", "PASSWORD_CLAIM_SECRET_BLOCK": "[secret_block]", "TIMESTAMP": [timestamp], "USERNAME": "[username]"}
Add "DEVICE_KEY"
when you sign in with a remembered device.
"ChallengeName": "CUSTOM_CHALLENGE", "ChallengeResponses": {"USERNAME": "[username]", "ANSWER": "[challenge_answer]"}
Add "DEVICE_KEY"
when you sign in with a remembered device.
"ChallengeName": "NEW_PASSWORD_REQUIRED", "ChallengeResponses": {"NEW_PASSWORD": "[new_password]", "USERNAME": "[username]"}
To set any required attributes that InitiateAuth
returned in an
requiredAttributes
parameter, add
"userAttributes.[attribute_name]": "[attribute_value]"
. This parameter can also set values
for writable attributes that aren't required by your user pool.
In a 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.
"ChallengeName": "SOFTWARE_TOKEN_MFA", "ChallengeResponses": {"USERNAME": "[username]", "SOFTWARE_TOKEN_MFA_CODE": [authenticator_code]}
"ChallengeName": "DEVICE_SRP_AUTH", "ChallengeResponses": {"USERNAME": "[username]", "DEVICE_KEY": "[device_key]", "SRP_A": "[srp_a]"}
"ChallengeName": "DEVICE_PASSWORD_VERIFIER", "ChallengeResponses": {"DEVICE_KEY": "[device_key]", "PASSWORD_CLAIM_SIGNATURE": "[claim_signature]", "PASSWORD_CLAIM_SECRET_BLOCK": "[secret_block]", "TIMESTAMP": [timestamp], "USERNAME": "[username]"}
"ChallengeName": "MFA_SETUP", "ChallengeResponses": {"USERNAME": "[username]"}, "SESSION": "[Session ID from VerifySoftwareToken]"
"ChallengeName": "SELECT_MFA_TYPE", "ChallengeResponses": {"USERNAME": "[username]", "ANSWER": "[SMS_MFA or SOFTWARE_TOKEN_MFA]"}
For more information about SECRET_HASH
, see Computing secret hash values. For information about DEVICE_KEY
, see Working with user devices in your user pool.
public void setChallengeResponses(Map<String,String> 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.
You must provide a SECRET_HASH parameter in all challenge responses to an app client that has a client secret.
"ChallengeName": "SMS_MFA", "ChallengeResponses": {"SMS_MFA_CODE": "[SMS_code]", "USERNAME": "[username]"}
"ChallengeName": "PASSWORD_VERIFIER", "ChallengeResponses": {"PASSWORD_CLAIM_SIGNATURE": "[claim_signature]", "PASSWORD_CLAIM_SECRET_BLOCK": "[secret_block]", "TIMESTAMP": [timestamp], "USERNAME": "[username]"}
Add "DEVICE_KEY"
when you sign in with a remembered device.
"ChallengeName": "CUSTOM_CHALLENGE", "ChallengeResponses": {"USERNAME": "[username]", "ANSWER": "[challenge_answer]"}
Add "DEVICE_KEY"
when you sign in with a remembered device.
"ChallengeName": "NEW_PASSWORD_REQUIRED", "ChallengeResponses": {"NEW_PASSWORD": "[new_password]", "USERNAME": "[username]"}
To set any required attributes that InitiateAuth
returned in an requiredAttributes
parameter, add "userAttributes.[attribute_name]": "[attribute_value]"
. This parameter can also set
values for writable attributes that aren't required by your user pool.
In a 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.
"ChallengeName": "SOFTWARE_TOKEN_MFA", "ChallengeResponses": {"USERNAME": "[username]", "SOFTWARE_TOKEN_MFA_CODE": [authenticator_code]}
"ChallengeName": "DEVICE_SRP_AUTH", "ChallengeResponses": {"USERNAME": "[username]", "DEVICE_KEY": "[device_key]", "SRP_A": "[srp_a]"}
"ChallengeName": "DEVICE_PASSWORD_VERIFIER", "ChallengeResponses": {"DEVICE_KEY": "[device_key]", "PASSWORD_CLAIM_SIGNATURE": "[claim_signature]", "PASSWORD_CLAIM_SECRET_BLOCK": "[secret_block]", "TIMESTAMP": [timestamp], "USERNAME": "[username]"}
"ChallengeName": "MFA_SETUP", "ChallengeResponses": {"USERNAME": "[username]"}, "SESSION": "[Session ID from VerifySoftwareToken]"
"ChallengeName": "SELECT_MFA_TYPE", "ChallengeResponses": {"USERNAME": "[username]", "ANSWER": "[SMS_MFA or SOFTWARE_TOKEN_MFA]"}
For more information about SECRET_HASH
, see Computing secret hash values. For information about DEVICE_KEY
, see Working with user devices in your user pool.
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. You must provide a SECRET_HASH parameter in all challenge responses to an app client that has a client secret.
"ChallengeName": "SMS_MFA", "ChallengeResponses": {"SMS_MFA_CODE": "[SMS_code]", "USERNAME": "[username]"}
"ChallengeName": "PASSWORD_VERIFIER", "ChallengeResponses": {"PASSWORD_CLAIM_SIGNATURE": "[claim_signature]", "PASSWORD_CLAIM_SECRET_BLOCK": "[secret_block]", "TIMESTAMP": [timestamp], "USERNAME": "[username]"}
Add "DEVICE_KEY"
when you sign in with a remembered device.
"ChallengeName": "CUSTOM_CHALLENGE", "ChallengeResponses": {"USERNAME": "[username]", "ANSWER": "[challenge_answer]"}
Add "DEVICE_KEY"
when you sign in with a remembered device.
"ChallengeName": "NEW_PASSWORD_REQUIRED", "ChallengeResponses": {"NEW_PASSWORD": "[new_password]", "USERNAME": "[username]"}
To set any required attributes that InitiateAuth
returned in an
requiredAttributes
parameter, add
"userAttributes.[attribute_name]": "[attribute_value]"
. This parameter can also set values
for writable attributes that aren't required by your user pool.
In a 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.
"ChallengeName": "SOFTWARE_TOKEN_MFA", "ChallengeResponses": {"USERNAME": "[username]", "SOFTWARE_TOKEN_MFA_CODE": [authenticator_code]}
"ChallengeName": "DEVICE_SRP_AUTH", "ChallengeResponses": {"USERNAME": "[username]", "DEVICE_KEY": "[device_key]", "SRP_A": "[srp_a]"}
"ChallengeName": "DEVICE_PASSWORD_VERIFIER", "ChallengeResponses": {"DEVICE_KEY": "[device_key]", "PASSWORD_CLAIM_SIGNATURE": "[claim_signature]", "PASSWORD_CLAIM_SECRET_BLOCK": "[secret_block]", "TIMESTAMP": [timestamp], "USERNAME": "[username]"}
"ChallengeName": "MFA_SETUP", "ChallengeResponses": {"USERNAME": "[username]"}, "SESSION": "[Session ID from VerifySoftwareToken]"
"ChallengeName": "SELECT_MFA_TYPE", "ChallengeResponses": {"USERNAME": "[username]", "ANSWER": "[SMS_MFA or SOFTWARE_TOKEN_MFA]"}
For more information about SECRET_HASH
, see Computing secret hash values. For information about DEVICE_KEY
, see Working with user devices in your user pool.
public RespondToAuthChallengeRequest withChallengeResponses(Map<String,String> 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.
You must provide a SECRET_HASH parameter in all challenge responses to an app client that has a client secret.
"ChallengeName": "SMS_MFA", "ChallengeResponses": {"SMS_MFA_CODE": "[SMS_code]", "USERNAME": "[username]"}
"ChallengeName": "PASSWORD_VERIFIER", "ChallengeResponses": {"PASSWORD_CLAIM_SIGNATURE": "[claim_signature]", "PASSWORD_CLAIM_SECRET_BLOCK": "[secret_block]", "TIMESTAMP": [timestamp], "USERNAME": "[username]"}
Add "DEVICE_KEY"
when you sign in with a remembered device.
"ChallengeName": "CUSTOM_CHALLENGE", "ChallengeResponses": {"USERNAME": "[username]", "ANSWER": "[challenge_answer]"}
Add "DEVICE_KEY"
when you sign in with a remembered device.
"ChallengeName": "NEW_PASSWORD_REQUIRED", "ChallengeResponses": {"NEW_PASSWORD": "[new_password]", "USERNAME": "[username]"}
To set any required attributes that InitiateAuth
returned in an requiredAttributes
parameter, add "userAttributes.[attribute_name]": "[attribute_value]"
. This parameter can also set
values for writable attributes that aren't required by your user pool.
In a 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.
"ChallengeName": "SOFTWARE_TOKEN_MFA", "ChallengeResponses": {"USERNAME": "[username]", "SOFTWARE_TOKEN_MFA_CODE": [authenticator_code]}
"ChallengeName": "DEVICE_SRP_AUTH", "ChallengeResponses": {"USERNAME": "[username]", "DEVICE_KEY": "[device_key]", "SRP_A": "[srp_a]"}
"ChallengeName": "DEVICE_PASSWORD_VERIFIER", "ChallengeResponses": {"DEVICE_KEY": "[device_key]", "PASSWORD_CLAIM_SIGNATURE": "[claim_signature]", "PASSWORD_CLAIM_SECRET_BLOCK": "[secret_block]", "TIMESTAMP": [timestamp], "USERNAME": "[username]"}
"ChallengeName": "MFA_SETUP", "ChallengeResponses": {"USERNAME": "[username]"}, "SESSION": "[Session ID from VerifySoftwareToken]"
"ChallengeName": "SELECT_MFA_TYPE", "ChallengeResponses": {"USERNAME": "[username]", "ANSWER": "[SMS_MFA or SOFTWARE_TOKEN_MFA]"}
For more information about SECRET_HASH
, see Computing secret hash values. For information about DEVICE_KEY
, see Working with user devices in your user pool.
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. You must provide a SECRET_HASH parameter in all challenge responses to an app client that has a client secret.
"ChallengeName": "SMS_MFA", "ChallengeResponses": {"SMS_MFA_CODE": "[SMS_code]", "USERNAME": "[username]"}
"ChallengeName": "PASSWORD_VERIFIER", "ChallengeResponses": {"PASSWORD_CLAIM_SIGNATURE": "[claim_signature]", "PASSWORD_CLAIM_SECRET_BLOCK": "[secret_block]", "TIMESTAMP": [timestamp], "USERNAME": "[username]"}
Add "DEVICE_KEY"
when you sign in with a remembered device.
"ChallengeName": "CUSTOM_CHALLENGE", "ChallengeResponses": {"USERNAME": "[username]", "ANSWER": "[challenge_answer]"}
Add "DEVICE_KEY"
when you sign in with a remembered device.
"ChallengeName": "NEW_PASSWORD_REQUIRED", "ChallengeResponses": {"NEW_PASSWORD": "[new_password]", "USERNAME": "[username]"}
To set any required attributes that InitiateAuth
returned in an
requiredAttributes
parameter, add
"userAttributes.[attribute_name]": "[attribute_value]"
. This parameter can also set values
for writable attributes that aren't required by your user pool.
In a 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.
"ChallengeName": "SOFTWARE_TOKEN_MFA", "ChallengeResponses": {"USERNAME": "[username]", "SOFTWARE_TOKEN_MFA_CODE": [authenticator_code]}
"ChallengeName": "DEVICE_SRP_AUTH", "ChallengeResponses": {"USERNAME": "[username]", "DEVICE_KEY": "[device_key]", "SRP_A": "[srp_a]"}
"ChallengeName": "DEVICE_PASSWORD_VERIFIER", "ChallengeResponses": {"DEVICE_KEY": "[device_key]", "PASSWORD_CLAIM_SIGNATURE": "[claim_signature]", "PASSWORD_CLAIM_SECRET_BLOCK": "[secret_block]", "TIMESTAMP": [timestamp], "USERNAME": "[username]"}
"ChallengeName": "MFA_SETUP", "ChallengeResponses": {"USERNAME": "[username]"}, "SESSION": "[Session ID from VerifySoftwareToken]"
"ChallengeName": "SELECT_MFA_TYPE", "ChallengeResponses": {"USERNAME": "[username]", "ANSWER": "[SMS_MFA or SOFTWARE_TOKEN_MFA]"}
For more information about SECRET_HASH
, see Computing secret hash values. For information about DEVICE_KEY
, see Working with user devices in your user pool.
public RespondToAuthChallengeRequest addChallengeResponsesEntry(String key, String value)
public RespondToAuthChallengeRequest clearChallengeResponsesEntries()
public void setAnalyticsMetadata(AnalyticsMetadataType analyticsMetadata)
The Amazon Pinpoint analytics metadata that contributes to your metrics for RespondToAuthChallenge
calls.
analyticsMetadata
- The Amazon Pinpoint analytics metadata that contributes to your metrics for
RespondToAuthChallenge
calls.public AnalyticsMetadataType getAnalyticsMetadata()
The Amazon Pinpoint analytics metadata that contributes to your metrics for RespondToAuthChallenge
calls.
RespondToAuthChallenge
calls.public RespondToAuthChallengeRequest withAnalyticsMetadata(AnalyticsMetadataType analyticsMetadata)
The Amazon Pinpoint analytics metadata that contributes to your metrics for RespondToAuthChallenge
calls.
analyticsMetadata
- The Amazon Pinpoint analytics metadata that contributes to your metrics for
RespondToAuthChallenge
calls.public void setUserContextData(UserContextDataType userContextData)
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.
userContextData
- 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.public UserContextDataType getUserContextData()
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.
public RespondToAuthChallengeRequest withUserContextData(UserContextDataType userContextData)
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.
userContextData
- 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.public Map<String,String> getClientMetadata()
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 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.
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.
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 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.
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.
public void setClientMetadata(Map<String,String> 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 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 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.
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.
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 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
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.
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.
public RespondToAuthChallengeRequest withClientMetadata(Map<String,String> 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 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 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.
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.
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 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
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.
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.
public RespondToAuthChallengeRequest addClientMetadataEntry(String key, String value)
public RespondToAuthChallengeRequest clearClientMetadataEntries()
public String toString()
toString
in class Object
Object.toString()
public RespondToAuthChallengeRequest clone()
AmazonWebServiceRequest
clone
in class AmazonWebServiceRequest
Object.clone()