/* * Copyright 2018-2023 Amazon.com, Inc. or its affiliates. All Rights Reserved. * * Licensed under the Apache License, Version 2.0 (the "License"). You may not use this file except in compliance with * the License. A copy of the License is located at * * http://aws.amazon.com/apache2.0 * * or in the "license" file accompanying this file. This file is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR * CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions * and limitations under the License. */ package com.amazonaws.services.cognitoidp.model; import java.io.Serializable; import javax.annotation.Generated; import com.amazonaws.AmazonWebServiceRequest; /** *

* Initiates the authorization request, as an administrator. *

* * @see AWS API * Documentation */ @Generated("com.amazonaws:aws-java-sdk-code-generator") public class AdminInitiateAuthRequest extends com.amazonaws.AmazonWebServiceRequest implements Serializable, Cloneable { /** *

* The ID of the Amazon Cognito user pool. *

*/ private String userPoolId; /** *

* The app client ID. *

*/ private String clientId; /** *

* 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. *
*

*/ private String authFlow; /** *

* 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 REFRESH_TOKEN_AUTH/REFRESH_TOKEN: REFRESH_TOKEN (required), * SECRET_HASH (required if the app client is configured with a client secret), DEVICE_KEY * . *
*
*
* For ADMIN_NO_SRP_AUTH: USERNAME (required), SECRET_HASH (if app client is * configured with client secret), PASSWORD (required), 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). *
*

*/ private java.util.Map authParameters; /** *

* 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 *
*
*
* Verify auth challenge *
*

* For more information, see Customizing user pool Workflows with Lambda Triggers in the Amazon Cognito Developer Guide. *

* *

* When you use the ClientMetadata parameter, remember that Amazon Cognito won't do the following: *

*
* Store the ClientMetadata value. This data is available only to Lambda triggers that are assigned to a user pool * to support custom workflows. If your user pool configuration doesn't include triggers, the ClientMetadata * parameter serves no purpose. *
*
*
* Validate the ClientMetadata value. *
*
*
* Encrypt the ClientMetadata value. Don't use Amazon Cognito to provide sensitive information. *
*

* */ private java.util.Map clientMetadata; /** *

* The analytics metadata for collecting Amazon Pinpoint metrics for AdminInitiateAuth calls. *

*/ private AnalyticsMetadataType analyticsMetadata; /** *

* 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. *

*/ private ContextDataType contextData; /** *

* The ID of the Amazon Cognito user pool. *

* * @param userPoolId * The ID of the Amazon Cognito user pool. */ public void setUserPoolId(String userPoolId) { this.userPoolId = userPoolId; } /** *

* The ID of the Amazon Cognito user pool. *

* * @return The ID of the Amazon Cognito user pool. */ public String getUserPoolId() { return this.userPoolId; } /** *

* The ID of the Amazon Cognito user pool. *

* * @param userPoolId * The ID of the Amazon Cognito user pool. * @return Returns a reference to this object so that method calls can be chained together. */ public AdminInitiateAuthRequest withUserPoolId(String userPoolId) { setUserPoolId(userPoolId); return this; } /** *

* The app client ID. *

* * @param clientId * The app client ID. */ public void setClientId(String clientId) { this.clientId = clientId; } /** *

* The app client ID. *

* * @return The app client ID. */ public String getClientId() { return this.clientId; } /** *

* The app client ID. *

* * @param clientId * The app client ID. * @return Returns a reference to this object so that method calls can be chained together. */ public AdminInitiateAuthRequest withClientId(String clientId) { setClientId(clientId); return this; } /** *

* 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. *
*

* * @param 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. *
*

* 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. *
*

* 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. *
*

* 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. *
*

* 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. *
*

* 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 REFRESH_TOKEN_AUTH/REFRESH_TOKEN: REFRESH_TOKEN (required), * SECRET_HASH (required if the app client is configured with a client secret), DEVICE_KEY * . *
*
*
* For ADMIN_NO_SRP_AUTH: USERNAME (required), SECRET_HASH (if app client is * configured with client secret), PASSWORD (required), 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). *
*

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 ADMIN_NO_SRP_AUTH: USERNAME (required), SECRET_HASH (if app * client is configured with client secret), PASSWORD (required), 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). *
*

getAuthParameters() { return 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 REFRESH_TOKEN_AUTH/REFRESH_TOKEN: REFRESH_TOKEN (required), * SECRET_HASH (required if the app client is configured with a client secret), DEVICE_KEY * . *
*
*
* For ADMIN_NO_SRP_AUTH: USERNAME (required), SECRET_HASH (if app client is * configured with client secret), PASSWORD (required), 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). *
*

* * @param 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 REFRESH_TOKEN_AUTH/REFRESH_TOKEN: REFRESH_TOKEN (required), * SECRET_HASH (required if the app client is configured with a client secret), * DEVICE_KEY. *
*
*
* For ADMIN_NO_SRP_AUTH: USERNAME (required), SECRET_HASH (if app * client is configured with client secret), PASSWORD (required), 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). *
*

authParameters) { this.authParameters = 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 REFRESH_TOKEN_AUTH/REFRESH_TOKEN: REFRESH_TOKEN (required), * SECRET_HASH (required if the app client is configured with a client secret), DEVICE_KEY * . *
*
*
* For ADMIN_NO_SRP_AUTH: USERNAME (required), SECRET_HASH (if app client is * configured with client secret), PASSWORD (required), 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). *
*

* * @param 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 REFRESH_TOKEN_AUTH/REFRESH_TOKEN: REFRESH_TOKEN (required), * SECRET_HASH (required if the app client is configured with a client secret), * DEVICE_KEY. *
*
*
* For ADMIN_NO_SRP_AUTH: USERNAME (required), SECRET_HASH (if app * client is configured with client secret), PASSWORD (required), 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). *
*

authParameters) { setAuthParameters(authParameters); return this; } /** * Add a single AuthParameters entry * * @see AdminInitiateAuthRequest#withAuthParameters * @returns a reference to this object so that method calls can be chained together. */ public AdminInitiateAuthRequest addAuthParametersEntry(String key, String value) { if (null == this.authParameters) { this.authParameters = new java.util.HashMap(); } if (this.authParameters.containsKey(key)) throw new IllegalArgumentException("Duplicated keys (" + key.toString() + ") are provided."); this.authParameters.put(key, value); return this; } /** * Removes all the entries added into AuthParameters. * * @return Returns a reference to this object so that method calls can be chained together. */ public AdminInitiateAuthRequest clearAuthParametersEntries() { this.authParameters = null; return this; } /** *

* A map of custom key-value pairs that you can provide as input for certain custom workflows that this action * triggers. *

*
* Pre signup *
*
*
* Pre authentication *
*
*
* User migration *
*

* When you use the AdminInitiateAuth API action, Amazon Cognito also invokes the functions for the following * triggers, but it doesn't provide the ClientMetadata value as input: *

*
* Post authentication *
*
*
* Custom message *
*
*
* Pre token generation *
*
*
* Create auth challenge *
*
*
* Define auth challenge *
*
*
* Verify auth challenge *
*

* For more information, see Customizing user pool Workflows with Lambda Triggers in the Amazon Cognito Developer Guide. *

* *

* When you use the ClientMetadata parameter, remember that Amazon Cognito won't do the following: *

*
* Store the ClientMetadata value. This data is available only to Lambda triggers that are assigned to a user pool * to support custom workflows. If your user pool configuration doesn't include triggers, the ClientMetadata * parameter serves no purpose. *
*
*
* Validate the ClientMetadata value. *
*
*
* Encrypt the ClientMetadata value. Don't use Amazon Cognito to provide sensitive information. *
*

* * * @return A map of custom key-value pairs that you can provide as input for certain custom workflows that this * action 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 *
*
*
* Verify auth challenge *
*

* For more information, see Customizing user pool Workflows with Lambda Triggers in the Amazon Cognito Developer Guide. *

* *

* When you use the ClientMetadata parameter, remember that Amazon Cognito won't do the following: *

*
* Store the ClientMetadata value. This data is available only to Lambda triggers that are assigned to a * user pool to support custom workflows. If your user pool configuration doesn't include triggers, the * ClientMetadata parameter serves no purpose. *
*
*
* Validate the ClientMetadata value. *
*
*
* Encrypt the ClientMetadata value. Don't use Amazon Cognito to provide sensitive information. *
*

*/ public java.util.Map getClientMetadata() { return clientMetadata; } /** *

* A map of custom key-value pairs that you can provide as input for certain custom workflows that this action * triggers. *

*
* Pre signup *
*
*
* Pre authentication *
*
*
* User migration *
*

* When you use the AdminInitiateAuth API action, Amazon Cognito also invokes the functions for the following * triggers, but it doesn't provide the ClientMetadata value as input: *

*
* Post authentication *
*
*
* Custom message *
*
*
* Pre token generation *
*
*
* Create auth challenge *
*
*
* Define auth challenge *
*
*
* Verify auth challenge *
*

* For more information, see Customizing user pool Workflows with Lambda Triggers in the Amazon Cognito Developer Guide. *

* *

* When you use the ClientMetadata parameter, remember that Amazon Cognito won't do the following: *

*
* Store the ClientMetadata value. This data is available only to Lambda triggers that are assigned to a user pool * to support custom workflows. If your user pool configuration doesn't include triggers, the ClientMetadata * parameter serves no purpose. *
*
*
* Validate the ClientMetadata value. *
*
*
* Encrypt the ClientMetadata value. Don't use Amazon Cognito to provide sensitive information. *
*

* * * @param clientMetadata * A map of custom key-value pairs that you can provide as input for certain custom workflows that this * action 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 *
*
*
* Verify auth challenge *
*

* For more information, see Customizing user pool Workflows with Lambda Triggers in the Amazon Cognito Developer Guide. *

* *

* When you use the ClientMetadata parameter, remember that Amazon Cognito won't do the following: *

*
* Store the ClientMetadata value. This data is available only to Lambda triggers that are assigned to a user * pool to support custom workflows. If your user pool configuration doesn't include triggers, the * ClientMetadata parameter serves no purpose. *
*
*
* Validate the ClientMetadata value. *
*
*
* Encrypt the ClientMetadata value. Don't use Amazon Cognito to provide sensitive information. *
*

*/ public void setClientMetadata(java.util.Map clientMetadata) { this.clientMetadata = clientMetadata; } /** *

* A map of custom key-value pairs that you can provide as input for certain custom workflows that this action * triggers. *

*
* Pre signup *
*
*
* Pre authentication *
*
*
* User migration *
*

* When you use the AdminInitiateAuth API action, Amazon Cognito also invokes the functions for the following * triggers, but it doesn't provide the ClientMetadata value as input: *

*
* Post authentication *
*
*
* Custom message *
*
*
* Pre token generation *
*
*
* Create auth challenge *
*
*
* Define auth challenge *
*
*
* Verify auth challenge *
*

* For more information, see Customizing user pool Workflows with Lambda Triggers in the Amazon Cognito Developer Guide. *

* *

* When you use the ClientMetadata parameter, remember that Amazon Cognito won't do the following: *

*
* Store the ClientMetadata value. This data is available only to Lambda triggers that are assigned to a user pool * to support custom workflows. If your user pool configuration doesn't include triggers, the ClientMetadata * parameter serves no purpose. *
*
*
* Validate the ClientMetadata value. *
*
*
* Encrypt the ClientMetadata value. Don't use Amazon Cognito to provide sensitive information. *
*

* * * @param clientMetadata * A map of custom key-value pairs that you can provide as input for certain custom workflows that this * action 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 *
*
*
* Verify auth challenge *
*

* For more information, see Customizing user pool Workflows with Lambda Triggers in the Amazon Cognito Developer Guide. *

* *

* When you use the ClientMetadata parameter, remember that Amazon Cognito won't do the following: *

*
* Store the ClientMetadata value. This data is available only to Lambda triggers that are assigned to a user * pool to support custom workflows. If your user pool configuration doesn't include triggers, the * ClientMetadata parameter serves no purpose. *
*
*
* Validate the ClientMetadata value. *
*
*
* Encrypt the ClientMetadata value. Don't use Amazon Cognito to provide sensitive information. *
*

* @return Returns a reference to this object so that method calls can be chained together. */ public AdminInitiateAuthRequest withClientMetadata(java.util.Map clientMetadata) { setClientMetadata(clientMetadata); return this; } /** * Add a single ClientMetadata entry * * @see AdminInitiateAuthRequest#withClientMetadata * @returns a reference to this object so that method calls can be chained together. */ public AdminInitiateAuthRequest addClientMetadataEntry(String key, String value) { if (null == this.clientMetadata) { this.clientMetadata = new java.util.HashMap(); } if (this.clientMetadata.containsKey(key)) throw new IllegalArgumentException("Duplicated keys (" + key.toString() + ") are provided."); this.clientMetadata.put(key, value); return this; } /** * Removes all the entries added into ClientMetadata. * * @return Returns a reference to this object so that method calls can be chained together. */ public AdminInitiateAuthRequest clearClientMetadataEntries() { this.clientMetadata = null; return this; } /** *

* The analytics metadata for collecting Amazon Pinpoint metrics for AdminInitiateAuth calls. *

* * @param analyticsMetadata * The analytics metadata for collecting Amazon Pinpoint metrics for AdminInitiateAuth calls. */ public void setAnalyticsMetadata(AnalyticsMetadataType analyticsMetadata) { this.analyticsMetadata = analyticsMetadata; } /** *

* The analytics metadata for collecting Amazon Pinpoint metrics for AdminInitiateAuth calls. *

* * @return The analytics metadata for collecting Amazon Pinpoint metrics for AdminInitiateAuth calls. */ public AnalyticsMetadataType getAnalyticsMetadata() { return this.analyticsMetadata; } /** *

* The analytics metadata for collecting Amazon Pinpoint metrics for AdminInitiateAuth calls. *

* * @param analyticsMetadata * The analytics metadata for collecting Amazon Pinpoint metrics for AdminInitiateAuth calls. * @return Returns a reference to this object so that method calls can be chained together. */ public AdminInitiateAuthRequest withAnalyticsMetadata(AnalyticsMetadataType analyticsMetadata) { setAnalyticsMetadata(analyticsMetadata); return this; } /** *

* * @return 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() { return this.contextData; } /** *

* * @param 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. * @return Returns a reference to this object so that method calls can be chained together. */ public AdminInitiateAuthRequest withContextData(ContextDataType contextData) { setContextData(contextData); return this; } /** * Returns a string representation of this object. This is useful for testing and debugging. Sensitive data will be * redacted from this string using a placeholder value. * * @return A string representation of this object. * * @see java.lang.Object#toString() */ @Override public String toString() { StringBuilder sb = new StringBuilder(); sb.append("{"); if (getUserPoolId() != null) sb.append("UserPoolId: ").append(getUserPoolId()).append(","); if (getClientId() != null) sb.append("ClientId: ").append("***Sensitive Data Redacted***").append(","); if (getAuthFlow() != null) sb.append("AuthFlow: ").append(getAuthFlow()).append(","); if (getAuthParameters() != null) sb.append("AuthParameters: ").append("***Sensitive Data Redacted***").append(","); if (getClientMetadata() != null) sb.append("ClientMetadata: ").append(getClientMetadata()).append(","); if (getAnalyticsMetadata() != null) sb.append("AnalyticsMetadata: ").append(getAnalyticsMetadata()).append(","); if (getContextData() != null) sb.append("ContextData: ").append(getContextData()); sb.append("}"); return sb.toString(); } @Override public boolean equals(Object obj) { if (this == obj) return true; if (obj == null) return false; if (obj instanceof AdminInitiateAuthRequest == false) return false; AdminInitiateAuthRequest other = (AdminInitiateAuthRequest) obj; if (other.getUserPoolId() == null ^ this.getUserPoolId() == null) return false; if (other.getUserPoolId() != null && other.getUserPoolId().equals(this.getUserPoolId()) == false) return false; if (other.getClientId() == null ^ this.getClientId() == null) return false; if (other.getClientId() != null && other.getClientId().equals(this.getClientId()) == false) return false; if (other.getAuthFlow() == null ^ this.getAuthFlow() == null) return false; if (other.getAuthFlow() != null && other.getAuthFlow().equals(this.getAuthFlow()) == false) return false; if (other.getAuthParameters() == null ^ this.getAuthParameters() == null) return false; if (other.getAuthParameters() != null && other.getAuthParameters().equals(this.getAuthParameters()) == false) return false; if (other.getClientMetadata() == null ^ this.getClientMetadata() == null) return false; if (other.getClientMetadata() != null && other.getClientMetadata().equals(this.getClientMetadata()) == false) return false; if (other.getAnalyticsMetadata() == null ^ this.getAnalyticsMetadata() == null) return false; if (other.getAnalyticsMetadata() != null && other.getAnalyticsMetadata().equals(this.getAnalyticsMetadata()) == false) return false; if (other.getContextData() == null ^ this.getContextData() == null) return false; if (other.getContextData() != null && other.getContextData().equals(this.getContextData()) == false) return false; return true; } @Override public int hashCode() { final int prime = 31; int hashCode = 1; hashCode = prime * hashCode + ((getUserPoolId() == null) ? 0 : getUserPoolId().hashCode()); hashCode = prime * hashCode + ((getClientId() == null) ? 0 : getClientId().hashCode()); hashCode = prime * hashCode + ((getAuthFlow() == null) ? 0 : getAuthFlow().hashCode()); hashCode = prime * hashCode + ((getAuthParameters() == null) ? 0 : getAuthParameters().hashCode()); hashCode = prime * hashCode + ((getClientMetadata() == null) ? 0 : getClientMetadata().hashCode()); hashCode = prime * hashCode + ((getAnalyticsMetadata() == null) ? 0 : getAnalyticsMetadata().hashCode()); hashCode = prime * hashCode + ((getContextData() == null) ? 0 : getContextData().hashCode()); return hashCode; } @Override public AdminInitiateAuthRequest clone() { return (AdminInitiateAuthRequest) super.clone(); } }