public class InitiateAuthRequest extends AmazonWebServiceRequest implements Serializable
Initiates the authentication flow.
| Constructor and Description |
|---|
InitiateAuthRequest() |
| Modifier and Type | Method and Description |
|---|---|
InitiateAuthRequest |
addAuthParametersEntry(String key,
String value)
The authentication parameters.
|
InitiateAuthRequest |
addClientMetadataEntry(String key,
String value)
A map of custom key-value pairs that you can provide as input for certain
custom workflows that this action triggers.
|
InitiateAuthRequest |
clearAuthParametersEntries()
Removes all the entries added into AuthParameters.
|
InitiateAuthRequest |
clearClientMetadataEntries()
Removes all the entries added into ClientMetadata.
|
boolean |
equals(Object obj) |
AnalyticsMetadataType |
getAnalyticsMetadata()
The Amazon Pinpoint analytics metadata for collecting metrics for
InitiateAuth calls. |
String |
getAuthFlow()
The authentication flow for this call to execute.
|
Map<String,String> |
getAuthParameters()
The authentication parameters.
|
String |
getClientId()
The app client ID.
|
Map<String,String> |
getClientMetadata()
A map of custom key-value pairs that you can provide as input for certain
custom workflows that this action triggers.
|
UserContextDataType |
getUserContextData()
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.
|
int |
hashCode() |
void |
setAnalyticsMetadata(AnalyticsMetadataType analyticsMetadata)
The Amazon Pinpoint analytics metadata for collecting metrics for
InitiateAuth calls. |
void |
setAuthFlow(AuthFlowType authFlow)
The authentication flow for this call to execute.
|
void |
setAuthFlow(String authFlow)
The authentication flow for this call to execute.
|
void |
setAuthParameters(Map<String,String> authParameters)
The authentication parameters.
|
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 certain
custom workflows that this action triggers.
|
void |
setUserContextData(UserContextDataType userContextData)
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.
|
String |
toString()
Returns a string representation of this object; useful for testing and
debugging.
|
InitiateAuthRequest |
withAnalyticsMetadata(AnalyticsMetadataType analyticsMetadata)
The Amazon Pinpoint analytics metadata for collecting metrics for
InitiateAuth calls. |
InitiateAuthRequest |
withAuthFlow(AuthFlowType authFlow)
The authentication flow for this call to execute.
|
InitiateAuthRequest |
withAuthFlow(String authFlow)
The authentication flow for this call to execute.
|
InitiateAuthRequest |
withAuthParameters(Map<String,String> authParameters)
The authentication parameters.
|
InitiateAuthRequest |
withClientId(String clientId)
The app client ID.
|
InitiateAuthRequest |
withClientMetadata(Map<String,String> clientMetadata)
A map of custom key-value pairs that you can provide as input for certain
custom workflows that this action triggers.
|
InitiateAuthRequest |
withUserContextData(UserContextDataType userContextData)
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.
|
clone, copyBaseTo, getCloneRoot, getCloneSource, getGeneralProgressListener, getRequestClientOptions, getRequestCredentials, getRequestMetricCollector, setGeneralProgressListener, setRequestCredentials, setRequestMetricCollector, withGeneralProgressListener, withRequestMetricCollectorpublic String getAuthFlow()
The authentication flow for this call to execute. The API action will depend on this value. For example:
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 SRP variables to be used for next
challenge execution.
USER_PASSWORD_AUTH will take in USERNAME and
PASSWORD and return the next challenge or tokens.
Valid values include:
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; USERNAME
and PASSWORD are passed directly. If a user migration Lambda trigger is
set, this flow will invoke the user migration Lambda if the USERNAME is
not found in the user pool.
ADMIN_USER_PASSWORD_AUTH: Admin-based user password
authentication. This replaces the ADMIN_NO_SRP_AUTH
authentication flow. In this flow, Cognito receives the password in the
request instead of using the SRP process to verify passwords.
ADMIN_NO_SRP_AUTH is not a valid value.
Constraints:
Allowed Values: USER_SRP_AUTH, REFRESH_TOKEN_AUTH, REFRESH_TOKEN,
CUSTOM_AUTH, ADMIN_NO_SRP_AUTH, USER_PASSWORD_AUTH,
ADMIN_USER_PASSWORD_AUTH
The authentication flow for this call to execute. The API action will depend on this value. For example:
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 SRP variables to be used for
next challenge execution.
USER_PASSWORD_AUTH will take in
USERNAME and PASSWORD and return the
next challenge or tokens.
Valid values include:
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;
USERNAME and PASSWORD are passed directly. If a user migration
Lambda trigger is set, this flow will invoke the user migration
Lambda if the USERNAME is not found in the user pool.
ADMIN_USER_PASSWORD_AUTH: Admin-based user password
authentication. This replaces the ADMIN_NO_SRP_AUTH
authentication flow. In this flow, Cognito receives the password
in the request instead of using the SRP process to verify
passwords.
ADMIN_NO_SRP_AUTH is not a valid value.
AuthFlowTypepublic void setAuthFlow(String authFlow)
The authentication flow for this call to execute. The API action will depend on this value. For example:
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 SRP variables to be used for next
challenge execution.
USER_PASSWORD_AUTH will take in USERNAME and
PASSWORD and return the next challenge or tokens.
Valid values include:
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; USERNAME
and PASSWORD are passed directly. If a user migration Lambda trigger is
set, this flow will invoke the user migration Lambda if the USERNAME is
not found in the user pool.
ADMIN_USER_PASSWORD_AUTH: Admin-based user password
authentication. This replaces the ADMIN_NO_SRP_AUTH
authentication flow. In this flow, Cognito receives the password in the
request instead of using the SRP process to verify passwords.
ADMIN_NO_SRP_AUTH is not a valid value.
Constraints:
Allowed Values: USER_SRP_AUTH, REFRESH_TOKEN_AUTH, REFRESH_TOKEN,
CUSTOM_AUTH, ADMIN_NO_SRP_AUTH, USER_PASSWORD_AUTH,
ADMIN_USER_PASSWORD_AUTH
authFlow - The authentication flow for this call to execute. The API action will depend on this value. For example:
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 SRP variables to be used
for next challenge execution.
USER_PASSWORD_AUTH will take in
USERNAME and PASSWORD and return the
next challenge or tokens.
Valid values include:
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;
USERNAME and PASSWORD are passed directly. If a user migration
Lambda trigger is set, this flow will invoke the user
migration Lambda if the USERNAME is not found in the user
pool.
ADMIN_USER_PASSWORD_AUTH: Admin-based user
password authentication. This replaces the
ADMIN_NO_SRP_AUTH authentication flow. In this
flow, Cognito receives the password in the request instead of
using the SRP process to verify passwords.
ADMIN_NO_SRP_AUTH is not a valid value.
AuthFlowTypepublic InitiateAuthRequest withAuthFlow(String authFlow)
The authentication flow for this call to execute. The API action will depend on this value. For example:
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 SRP variables to be used for next
challenge execution.
USER_PASSWORD_AUTH will take in USERNAME and
PASSWORD and return the next challenge or tokens.
Valid values include:
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; USERNAME
and PASSWORD are passed directly. If a user migration Lambda trigger is
set, this flow will invoke the user migration Lambda if the USERNAME is
not found in the user pool.
ADMIN_USER_PASSWORD_AUTH: Admin-based user password
authentication. This replaces the ADMIN_NO_SRP_AUTH
authentication flow. In this flow, Cognito receives the password in the
request instead of using the SRP process to verify passwords.
ADMIN_NO_SRP_AUTH is not a valid value.
Returns a reference to this object so that method calls can be chained together.
Constraints:
Allowed Values: USER_SRP_AUTH, REFRESH_TOKEN_AUTH, REFRESH_TOKEN,
CUSTOM_AUTH, ADMIN_NO_SRP_AUTH, USER_PASSWORD_AUTH,
ADMIN_USER_PASSWORD_AUTH
authFlow - The authentication flow for this call to execute. The API action will depend on this value. For example:
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 SRP variables to be used
for next challenge execution.
USER_PASSWORD_AUTH will take in
USERNAME and PASSWORD and return the
next challenge or tokens.
Valid values include:
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;
USERNAME and PASSWORD are passed directly. If a user migration
Lambda trigger is set, this flow will invoke the user
migration Lambda if the USERNAME is not found in the user
pool.
ADMIN_USER_PASSWORD_AUTH: Admin-based user
password authentication. This replaces the
ADMIN_NO_SRP_AUTH authentication flow. In this
flow, Cognito receives the password in the request instead of
using the SRP process to verify passwords.
ADMIN_NO_SRP_AUTH is not a valid value.
AuthFlowTypepublic void setAuthFlow(AuthFlowType authFlow)
The authentication flow for this call to execute. The API action will depend on this value. For example:
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 SRP variables to be used for next
challenge execution.
USER_PASSWORD_AUTH will take in USERNAME and
PASSWORD and return the next challenge or tokens.
Valid values include:
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; USERNAME
and PASSWORD are passed directly. If a user migration Lambda trigger is
set, this flow will invoke the user migration Lambda if the USERNAME is
not found in the user pool.
ADMIN_USER_PASSWORD_AUTH: Admin-based user password
authentication. This replaces the ADMIN_NO_SRP_AUTH
authentication flow. In this flow, Cognito receives the password in the
request instead of using the SRP process to verify passwords.
ADMIN_NO_SRP_AUTH is not a valid value.
Constraints:
Allowed Values: USER_SRP_AUTH, REFRESH_TOKEN_AUTH, REFRESH_TOKEN,
CUSTOM_AUTH, ADMIN_NO_SRP_AUTH, USER_PASSWORD_AUTH,
ADMIN_USER_PASSWORD_AUTH
authFlow - The authentication flow for this call to execute. The API action will depend on this value. For example:
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 SRP variables to be used
for next challenge execution.
USER_PASSWORD_AUTH will take in
USERNAME and PASSWORD and return the
next challenge or tokens.
Valid values include:
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;
USERNAME and PASSWORD are passed directly. If a user migration
Lambda trigger is set, this flow will invoke the user
migration Lambda if the USERNAME is not found in the user
pool.
ADMIN_USER_PASSWORD_AUTH: Admin-based user
password authentication. This replaces the
ADMIN_NO_SRP_AUTH authentication flow. In this
flow, Cognito receives the password in the request instead of
using the SRP process to verify passwords.
ADMIN_NO_SRP_AUTH is not a valid value.
AuthFlowTypepublic InitiateAuthRequest withAuthFlow(AuthFlowType authFlow)
The authentication flow for this call to execute. The API action will depend on this value. For example:
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 SRP variables to be used for next
challenge execution.
USER_PASSWORD_AUTH will take in USERNAME and
PASSWORD and return the next challenge or tokens.
Valid values include:
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; USERNAME
and PASSWORD are passed directly. If a user migration Lambda trigger is
set, this flow will invoke the user migration Lambda if the USERNAME is
not found in the user pool.
ADMIN_USER_PASSWORD_AUTH: Admin-based user password
authentication. This replaces the ADMIN_NO_SRP_AUTH
authentication flow. In this flow, Cognito receives the password in the
request instead of using the SRP process to verify passwords.
ADMIN_NO_SRP_AUTH is not a valid value.
Returns a reference to this object so that method calls can be chained together.
Constraints:
Allowed Values: USER_SRP_AUTH, REFRESH_TOKEN_AUTH, REFRESH_TOKEN,
CUSTOM_AUTH, ADMIN_NO_SRP_AUTH, USER_PASSWORD_AUTH,
ADMIN_USER_PASSWORD_AUTH
authFlow - The authentication flow for this call to execute. The API action will depend on this value. For example:
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 SRP variables to be used
for next challenge execution.
USER_PASSWORD_AUTH will take in
USERNAME and PASSWORD and return the
next challenge or tokens.
Valid values include:
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;
USERNAME and PASSWORD are passed directly. If a user migration
Lambda trigger is set, this flow will invoke the user
migration Lambda if the USERNAME is not found in the user
pool.
ADMIN_USER_PASSWORD_AUTH: Admin-based user
password authentication. This replaces the
ADMIN_NO_SRP_AUTH authentication flow. In this
flow, Cognito receives the password in the request instead of
using the SRP process to verify passwords.
ADMIN_NO_SRP_AUTH is not a valid value.
AuthFlowTypepublic Map<String,String> getAuthParameters()
The authentication parameters. These are inputs corresponding to the
AuthFlow that you are invoking. The required values depend
on the value of AuthFlow:
For USER_SRP_AUTH: USERNAME (required),
SRP_A (required), SECRET_HASH (required if the
app client is configured with a client secret), DEVICE_KEY
For REFRESH_TOKEN_AUTH/REFRESH_TOKEN:
REFRESH_TOKEN (required), SECRET_HASH (required
if the app client is configured with a client secret),
DEVICE_KEY
For CUSTOM_AUTH: USERNAME (required),
SECRET_HASH (if app client is configured with client
secret), DEVICE_KEY
The authentication parameters. These are inputs corresponding to
the AuthFlow that you are invoking. The required
values depend on the value of AuthFlow:
For USER_SRP_AUTH: USERNAME (required),
SRP_A (required), SECRET_HASH (required
if the app client is configured with a client secret),
DEVICE_KEY
For REFRESH_TOKEN_AUTH/REFRESH_TOKEN:
REFRESH_TOKEN (required), SECRET_HASH
(required if the app client is configured with a client secret),
DEVICE_KEY
For CUSTOM_AUTH: USERNAME (required),
SECRET_HASH (if app client is configured with client
secret), DEVICE_KEY
public void setAuthParameters(Map<String,String> authParameters)
The authentication parameters. These are inputs corresponding to the
AuthFlow that you are invoking. The required values depend
on the value of AuthFlow:
For USER_SRP_AUTH: USERNAME (required),
SRP_A (required), SECRET_HASH (required if the
app client is configured with a client secret), DEVICE_KEY
For REFRESH_TOKEN_AUTH/REFRESH_TOKEN:
REFRESH_TOKEN (required), SECRET_HASH (required
if the app client is configured with a client secret),
DEVICE_KEY
For CUSTOM_AUTH: USERNAME (required),
SECRET_HASH (if app client is configured with client
secret), DEVICE_KEY
authParameters -
The authentication parameters. These are inputs corresponding
to the AuthFlow that you are invoking. The
required values depend on the value of AuthFlow:
For USER_SRP_AUTH: USERNAME
(required), SRP_A (required),
SECRET_HASH (required if the app client is
configured with a client secret), DEVICE_KEY
For REFRESH_TOKEN_AUTH/REFRESH_TOKEN:
REFRESH_TOKEN (required),
SECRET_HASH (required if the app client is
configured with a client secret), DEVICE_KEY
For CUSTOM_AUTH: USERNAME
(required), SECRET_HASH (if app client is
configured with client secret), DEVICE_KEY
public InitiateAuthRequest withAuthParameters(Map<String,String> authParameters)
The authentication parameters. These are inputs corresponding to the
AuthFlow that you are invoking. The required values depend
on the value of AuthFlow:
For USER_SRP_AUTH: USERNAME (required),
SRP_A (required), SECRET_HASH (required if the
app client is configured with a client secret), DEVICE_KEY
For REFRESH_TOKEN_AUTH/REFRESH_TOKEN:
REFRESH_TOKEN (required), SECRET_HASH (required
if the app client is configured with a client secret),
DEVICE_KEY
For CUSTOM_AUTH: USERNAME (required),
SECRET_HASH (if app client is configured with client
secret), DEVICE_KEY
Returns a reference to this object so that method calls can be chained together.
authParameters -
The authentication parameters. These are inputs corresponding
to the AuthFlow that you are invoking. The
required values depend on the value of AuthFlow:
For USER_SRP_AUTH: USERNAME
(required), SRP_A (required),
SECRET_HASH (required if the app client is
configured with a client secret), DEVICE_KEY
For REFRESH_TOKEN_AUTH/REFRESH_TOKEN:
REFRESH_TOKEN (required),
SECRET_HASH (required if the app client is
configured with a client secret), DEVICE_KEY
For CUSTOM_AUTH: USERNAME
(required), SECRET_HASH (if app client is
configured with client secret), DEVICE_KEY
public InitiateAuthRequest addAuthParametersEntry(String key, String value)
The authentication parameters. These are inputs corresponding to the
AuthFlow that you are invoking. The required values depend
on the value of AuthFlow:
For USER_SRP_AUTH: USERNAME (required),
SRP_A (required), SECRET_HASH (required if the
app client is configured with a client secret), DEVICE_KEY
For REFRESH_TOKEN_AUTH/REFRESH_TOKEN:
REFRESH_TOKEN (required), SECRET_HASH (required
if the app client is configured with a client secret),
DEVICE_KEY
For CUSTOM_AUTH: USERNAME (required),
SECRET_HASH (if app client is configured with client
secret), DEVICE_KEY
The method adds a new key-value pair into AuthParameters parameter, and returns a reference to this object so that method calls can be chained together.
key - The key of the entry to be added into AuthParameters.value - The corresponding value of the entry to be added into
AuthParameters.public InitiateAuthRequest clearAuthParametersEntries()
Returns a reference to this object so that method calls can be chained together.
public Map<String,String> getClientMetadata()
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 AWS Lambda functions to user pool triggers. When you use the InitiateAuth API action, Amazon Cognito invokes the AWS 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 validationData attribute, which provides the data that you
assigned to the ClientMetadata parameter in your InitiateAuth request. In
your function code in AWS Lambda, you can process the
validationData value to enhance your workflow for your
specific needs.
When you use the InitiateAuth API action, Amazon Cognito also invokes the functions for the following triggers, but it does not 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.
Take the following limitations into consideration when you use the ClientMetadata parameter:
Amazon Cognito does not store the ClientMetadata value. This data is available only to AWS Lambda triggers that are assigned to a user pool to support custom workflows. If your user pool configuration does not include triggers, the ClientMetadata parameter serves no purpose.
Amazon Cognito does not validate the ClientMetadata value.
Amazon Cognito does not encrypt the the ClientMetadata value, so don't use it to provide sensitive information.
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 AWS Lambda functions to user pool triggers. When you use the InitiateAuth API action, Amazon Cognito invokes the AWS 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 validationData attribute, which
provides the data that you assigned to the ClientMetadata
parameter in your InitiateAuth request. In your function code in
AWS Lambda, you can process the validationData value
to enhance your workflow for your specific needs.
When you use the InitiateAuth API action, Amazon Cognito also invokes the functions for the following triggers, but it does not 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.
Take the following limitations into consideration when you use the ClientMetadata parameter:
Amazon Cognito does not store the ClientMetadata value. This data is available only to AWS Lambda triggers that are assigned to a user pool to support custom workflows. If your user pool configuration does not include triggers, the ClientMetadata parameter serves no purpose.
Amazon Cognito does not validate the ClientMetadata value.
Amazon Cognito does not encrypt the the ClientMetadata value, so don't use it 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 certain custom workflows that this action triggers.
You create custom workflows by assigning AWS Lambda functions to user pool triggers. When you use the InitiateAuth API action, Amazon Cognito invokes the AWS 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 validationData attribute, which provides the data that you
assigned to the ClientMetadata parameter in your InitiateAuth request. In
your function code in AWS Lambda, you can process the
validationData value to enhance your workflow for your
specific needs.
When you use the InitiateAuth API action, Amazon Cognito also invokes the functions for the following triggers, but it does not 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.
Take the following limitations into consideration when you use the ClientMetadata parameter:
Amazon Cognito does not store the ClientMetadata value. This data is available only to AWS Lambda triggers that are assigned to a user pool to support custom workflows. If your user pool configuration does not include triggers, the ClientMetadata parameter serves no purpose.
Amazon Cognito does not validate the ClientMetadata value.
Amazon Cognito does not encrypt the the ClientMetadata value, so don't use it to provide sensitive information.
clientMetadata - 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 AWS Lambda functions to user pool triggers. When you use the InitiateAuth API action, Amazon Cognito invokes the AWS 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 validationData
attribute, which provides the data that you assigned to the
ClientMetadata parameter in your InitiateAuth request. In your
function code in AWS Lambda, you can process the
validationData value to enhance your workflow for
your specific needs.
When you use the InitiateAuth API action, Amazon Cognito also invokes the functions for the following triggers, but it does not 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.
Take the following limitations into consideration when you use the ClientMetadata parameter:
Amazon Cognito does not store the ClientMetadata value. This data is available only to AWS Lambda triggers that are assigned to a user pool to support custom workflows. If your user pool configuration does not include triggers, the ClientMetadata parameter serves no purpose.
Amazon Cognito does not validate the ClientMetadata value.
Amazon Cognito does not encrypt the the ClientMetadata value, so don't use it to provide sensitive information.
public InitiateAuthRequest withClientMetadata(Map<String,String> clientMetadata)
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 AWS Lambda functions to user pool triggers. When you use the InitiateAuth API action, Amazon Cognito invokes the AWS 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 validationData attribute, which provides the data that you
assigned to the ClientMetadata parameter in your InitiateAuth request. In
your function code in AWS Lambda, you can process the
validationData value to enhance your workflow for your
specific needs.
When you use the InitiateAuth API action, Amazon Cognito also invokes the functions for the following triggers, but it does not 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.
Take the following limitations into consideration when you use the ClientMetadata parameter:
Amazon Cognito does not store the ClientMetadata value. This data is available only to AWS Lambda triggers that are assigned to a user pool to support custom workflows. If your user pool configuration does not include triggers, the ClientMetadata parameter serves no purpose.
Amazon Cognito does not validate the ClientMetadata value.
Amazon Cognito does not encrypt the the ClientMetadata value, so don't use it to provide sensitive information.
Returns a reference to this object so that method calls can be chained together.
clientMetadata - 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 AWS Lambda functions to user pool triggers. When you use the InitiateAuth API action, Amazon Cognito invokes the AWS 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 validationData
attribute, which provides the data that you assigned to the
ClientMetadata parameter in your InitiateAuth request. In your
function code in AWS Lambda, you can process the
validationData value to enhance your workflow for
your specific needs.
When you use the InitiateAuth API action, Amazon Cognito also invokes the functions for the following triggers, but it does not 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.
Take the following limitations into consideration when you use the ClientMetadata parameter:
Amazon Cognito does not store the ClientMetadata value. This data is available only to AWS Lambda triggers that are assigned to a user pool to support custom workflows. If your user pool configuration does not include triggers, the ClientMetadata parameter serves no purpose.
Amazon Cognito does not validate the ClientMetadata value.
Amazon Cognito does not encrypt the the ClientMetadata value, so don't use it to provide sensitive information.
public InitiateAuthRequest addClientMetadataEntry(String key, String value)
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 AWS Lambda functions to user pool triggers. When you use the InitiateAuth API action, Amazon Cognito invokes the AWS 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 validationData attribute, which provides the data that you
assigned to the ClientMetadata parameter in your InitiateAuth request. In
your function code in AWS Lambda, you can process the
validationData value to enhance your workflow for your
specific needs.
When you use the InitiateAuth API action, Amazon Cognito also invokes the functions for the following triggers, but it does not 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.
Take the following limitations into consideration when you use the ClientMetadata parameter:
Amazon Cognito does not store the ClientMetadata value. This data is available only to AWS Lambda triggers that are assigned to a user pool to support custom workflows. If your user pool configuration does not include triggers, the ClientMetadata parameter serves no purpose.
Amazon Cognito does not validate the ClientMetadata value.
Amazon Cognito does not encrypt the the ClientMetadata value, so don't use it to provide sensitive information.
The method adds a new key-value pair into ClientMetadata parameter, and returns a reference to this object so that method calls can be chained together.
key - The key of the entry to be added into ClientMetadata.value - The corresponding value of the entry to be added into
ClientMetadata.public InitiateAuthRequest clearClientMetadataEntries()
Returns a reference to this object so that method calls can be chained together.
public String getClientId()
The app client ID.
Constraints:
Length: 1 - 128
Pattern: [\w+]+
The app client ID.
public void setClientId(String clientId)
The app client ID.
Constraints:
Length: 1 - 128
Pattern: [\w+]+
clientId - The app client ID.
public InitiateAuthRequest withClientId(String clientId)
The app client ID.
Returns a reference to this object so that method calls can be chained together.
Constraints:
Length: 1 - 128
Pattern: [\w+]+
clientId - The app client ID.
public AnalyticsMetadataType getAnalyticsMetadata()
The Amazon Pinpoint analytics metadata for collecting metrics for
InitiateAuth calls.
The Amazon Pinpoint analytics metadata for collecting metrics for
InitiateAuth calls.
public void setAnalyticsMetadata(AnalyticsMetadataType analyticsMetadata)
The Amazon Pinpoint analytics metadata for collecting metrics for
InitiateAuth calls.
analyticsMetadata -
The Amazon Pinpoint analytics metadata for collecting metrics
for InitiateAuth calls.
public InitiateAuthRequest withAnalyticsMetadata(AnalyticsMetadataType analyticsMetadata)
The Amazon Pinpoint analytics metadata for collecting metrics for
InitiateAuth calls.
Returns a reference to this object so that method calls can be chained together.
analyticsMetadata -
The Amazon Pinpoint analytics metadata for collecting metrics
for InitiateAuth calls.
public UserContextDataType getUserContextData()
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.
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.
public void setUserContextData(UserContextDataType userContextData)
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.
userContextData - 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.
public InitiateAuthRequest withUserContextData(UserContextDataType userContextData)
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.
Returns a reference to this object so that method calls can be chained together.
userContextData - 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.
public String toString()
toString in class ObjectObject.toString()Copyright © 2020. All rights reserved.