@Generated(value="com.amazonaws:aws-java-sdk-code-generator") public class AdminInitiateAuthRequest extends AmazonWebServiceRequest implements Serializable, Cloneable
Initiates the authorization request, as an administrator.
NOOP
Constructor and Description |
---|
AdminInitiateAuthRequest() |
Modifier and Type | Method and Description |
---|---|
AdminInitiateAuthRequest |
addAuthParametersEntry(String key,
String value)
Add a single AuthParameters entry
|
AdminInitiateAuthRequest |
addClientMetadataEntry(String key,
String value)
Add a single ClientMetadata entry
|
AdminInitiateAuthRequest |
clearAuthParametersEntries()
Removes all the entries added into AuthParameters.
|
AdminInitiateAuthRequest |
clearClientMetadataEntries()
Removes all the entries added into ClientMetadata.
|
AdminInitiateAuthRequest |
clone()
Creates a shallow clone of this object for all fields except the handler context.
|
boolean |
equals(Object obj) |
AnalyticsMetadataType |
getAnalyticsMetadata()
The analytics metadata for collecting Amazon Pinpoint metrics for
AdminInitiateAuth calls. |
String |
getAuthFlow()
The authentication flow for this call to run.
|
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.
|
ContextDataType |
getContextData()
Contextual data about your user session, such as the device fingerprint, IP address, or location.
|
String |
getUserPoolId()
The ID of the Amazon Cognito user pool.
|
int |
hashCode() |
void |
setAnalyticsMetadata(AnalyticsMetadataType analyticsMetadata)
The analytics metadata for collecting Amazon Pinpoint metrics for
AdminInitiateAuth calls. |
void |
setAuthFlow(AuthFlowType authFlow)
The authentication flow for this call to run.
|
void |
setAuthFlow(String authFlow)
The authentication flow for this call to run.
|
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 |
setContextData(ContextDataType contextData)
Contextual data about your user session, such as the device fingerprint, IP address, or location.
|
void |
setUserPoolId(String userPoolId)
The ID of the Amazon Cognito user pool.
|
String |
toString()
Returns a string representation of this object.
|
AdminInitiateAuthRequest |
withAnalyticsMetadata(AnalyticsMetadataType analyticsMetadata)
The analytics metadata for collecting Amazon Pinpoint metrics for
AdminInitiateAuth calls. |
AdminInitiateAuthRequest |
withAuthFlow(AuthFlowType authFlow)
The authentication flow for this call to run.
|
AdminInitiateAuthRequest |
withAuthFlow(String authFlow)
The authentication flow for this call to run.
|
AdminInitiateAuthRequest |
withAuthParameters(Map<String,String> authParameters)
The authentication parameters.
|
AdminInitiateAuthRequest |
withClientId(String clientId)
The app client ID.
|
AdminInitiateAuthRequest |
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.
|
AdminInitiateAuthRequest |
withContextData(ContextDataType contextData)
Contextual data about your user session, such as the device fingerprint, IP address, or location.
|
AdminInitiateAuthRequest |
withUserPoolId(String userPoolId)
The ID of the Amazon Cognito user pool.
|
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 setUserPoolId(String userPoolId)
The ID of the Amazon Cognito user pool.
userPoolId
- The ID of the Amazon Cognito user pool.public String getUserPoolId()
The ID of the Amazon Cognito user pool.
public AdminInitiateAuthRequest withUserPoolId(String userPoolId)
The ID of the Amazon Cognito user pool.
userPoolId
- The ID of the Amazon Cognito user pool.public void setClientId(String clientId)
The app client ID.
clientId
- The app client ID.public String getClientId()
The app client ID.
public AdminInitiateAuthRequest withClientId(String clientId)
The app client ID.
clientId
- The app client ID.public void setAuthFlow(String authFlow)
The authentication flow for this call to run. 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 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.
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.
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
- The authentication flow for this call to run. 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 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.
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.
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.
AuthFlowType
public String getAuthFlow()
The authentication flow for this call to run. 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 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.
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.
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.
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.
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.
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.
AuthFlowType
public AdminInitiateAuthRequest withAuthFlow(String authFlow)
The authentication flow for this call to run. 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 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.
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.
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
- The authentication flow for this call to run. 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 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.
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.
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.
AuthFlowType
public void setAuthFlow(AuthFlowType authFlow)
The authentication flow for this call to run. 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 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.
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.
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
- The authentication flow for this call to run. 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 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.
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.
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.
AuthFlowType
public AdminInitiateAuthRequest withAuthFlow(AuthFlowType authFlow)
The authentication flow for this call to run. 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 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.
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.
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
- The authentication flow for this call to run. 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 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.
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.
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.
AuthFlowType
public Map<String,String> getAuthParameters()
The authentication parameters. These are inputs corresponding to the AuthFlow
that you're 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 ADMIN_USER_PASSWORD_AUTH
: USERNAME
(required), PASSWORD
(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
. To start the authentication flow with password
verification, include ChallengeName: SRP_A
and SRP_A: (The SRP_A Value)
.
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.
AuthFlow
that you're
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 ADMIN_USER_PASSWORD_AUTH
: USERNAME
(required), PASSWORD
(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
. To start the authentication flow with
password verification, include ChallengeName: SRP_A
and
SRP_A: (The SRP_A Value)
.
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 setAuthParameters(Map<String,String> authParameters)
The authentication parameters. These are inputs corresponding to the AuthFlow
that you're 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 ADMIN_USER_PASSWORD_AUTH
: USERNAME
(required), PASSWORD
(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
. To start the authentication flow with password
verification, include ChallengeName: SRP_A
and SRP_A: (The SRP_A Value)
.
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.
authParameters
- The authentication parameters. These are inputs corresponding to the AuthFlow
that you're
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 ADMIN_USER_PASSWORD_AUTH
: USERNAME
(required), PASSWORD
(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
. To start the authentication flow with password
verification, include ChallengeName: SRP_A
and SRP_A: (The SRP_A Value)
.
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 AdminInitiateAuthRequest withAuthParameters(Map<String,String> authParameters)
The authentication parameters. These are inputs corresponding to the AuthFlow
that you're 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 ADMIN_USER_PASSWORD_AUTH
: USERNAME
(required), PASSWORD
(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
. To start the authentication flow with password
verification, include ChallengeName: SRP_A
and SRP_A: (The SRP_A Value)
.
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.
authParameters
- The authentication parameters. These are inputs corresponding to the AuthFlow
that you're
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 ADMIN_USER_PASSWORD_AUTH
: USERNAME
(required), PASSWORD
(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
. To start the authentication flow with password
verification, include ChallengeName: SRP_A
and SRP_A: (The SRP_A Value)
.
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 AdminInitiateAuthRequest addAuthParametersEntry(String key, String value)
public AdminInitiateAuthRequest clearAuthParametersEntries()
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 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 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.
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
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 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 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.
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
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 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 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.
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
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 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 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.
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
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 AdminInitiateAuthRequest 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 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 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.
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
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 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 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.
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
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 AdminInitiateAuthRequest addClientMetadataEntry(String key, String value)
public AdminInitiateAuthRequest clearClientMetadataEntries()
public void setAnalyticsMetadata(AnalyticsMetadataType analyticsMetadata)
The analytics metadata for collecting Amazon Pinpoint metrics for AdminInitiateAuth
calls.
analyticsMetadata
- The analytics metadata for collecting Amazon Pinpoint metrics for AdminInitiateAuth
calls.public AnalyticsMetadataType getAnalyticsMetadata()
The analytics metadata for collecting Amazon Pinpoint metrics for AdminInitiateAuth
calls.
AdminInitiateAuth
calls.public AdminInitiateAuthRequest withAnalyticsMetadata(AnalyticsMetadataType analyticsMetadata)
The analytics metadata for collecting Amazon Pinpoint metrics for AdminInitiateAuth
calls.
analyticsMetadata
- The analytics metadata for collecting Amazon Pinpoint metrics for AdminInitiateAuth
calls.public void setContextData(ContextDataType contextData)
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.
contextData
- 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 ContextDataType getContextData()
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 AdminInitiateAuthRequest withContextData(ContextDataType contextData)
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.
contextData
- 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 String toString()
toString
in class Object
Object.toString()
public AdminInitiateAuthRequest clone()
AmazonWebServiceRequest
clone
in class AmazonWebServiceRequest
Object.clone()