/* * 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; /** *
* Represents the request to register a user. *
* * @see AWS API * Documentation */ @Generated("com.amazonaws:aws-java-sdk-code-generator") public class SignUpRequest extends com.amazonaws.AmazonWebServiceRequest implements Serializable, Cloneable { /** ** The ID of the client associated with the user pool. *
*/ private String clientId; /** ** A keyed-hash message authentication code (HMAC) calculated using the secret key of a user pool client and * username plus the client ID in the message. *
*/ private String secretHash; /** ** The user name of the user you want to register. *
*/ private String username; /** ** The password of the user you want to register. *
*/ private String password; /** ** An array of name-value pairs representing user attributes. *
*
* For custom attributes, you must prepend the custom:
prefix to the attribute name.
*
* The validation data in the request to register a user. *
*/ private java.util.List
* The Amazon Pinpoint analytics metadata that contributes to your metrics for SignUp
calls.
*
* 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 UserContextDataType userContextData; /** ** A map of custom key-value pairs that you can provide as input for any custom workflows that this action triggers. *
*
* You create custom workflows by assigning Lambda functions to user pool triggers. When you use the SignUp API
* action, Amazon Cognito invokes any functions that are assigned to the following triggers: pre sign-up,
* custom message, and post confirmation. When Amazon Cognito invokes any of these functions, it
* passes a JSON payload, which the function receives as input. This payload contains a clientMetadata
* attribute, which provides the data that you assigned to the ClientMetadata parameter in your SignUp request. In
* your function code in Lambda, you can process the clientMetadata
value to enhance your workflow for
* your specific needs.
*
* For more information, see Customizing user pool Workflows with Lambda Triggers in the Amazon Cognito Developer Guide. *
** When you use the ClientMetadata parameter, remember that Amazon Cognito won't do the following: *
** Store the ClientMetadata value. This data is available only to Lambda triggers that are assigned to a user pool * to support custom workflows. If your user pool configuration doesn't include triggers, the ClientMetadata * parameter serves no purpose. *
** Validate the ClientMetadata value. *
** Encrypt the ClientMetadata value. Don't use Amazon Cognito to provide sensitive information. *
** The ID of the client associated with the user pool. *
* * @param clientId * The ID of the client associated with the user pool. */ public void setClientId(String clientId) { this.clientId = clientId; } /** ** The ID of the client associated with the user pool. *
* * @return The ID of the client associated with the user pool. */ public String getClientId() { return this.clientId; } /** ** The ID of the client associated with the user pool. *
* * @param clientId * The ID of the client associated with the user pool. * @return Returns a reference to this object so that method calls can be chained together. */ public SignUpRequest withClientId(String clientId) { setClientId(clientId); return this; } /** ** A keyed-hash message authentication code (HMAC) calculated using the secret key of a user pool client and * username plus the client ID in the message. *
* * @param secretHash * A keyed-hash message authentication code (HMAC) calculated using the secret key of a user pool client and * username plus the client ID in the message. */ public void setSecretHash(String secretHash) { this.secretHash = secretHash; } /** ** A keyed-hash message authentication code (HMAC) calculated using the secret key of a user pool client and * username plus the client ID in the message. *
* * @return A keyed-hash message authentication code (HMAC) calculated using the secret key of a user pool client and * username plus the client ID in the message. */ public String getSecretHash() { return this.secretHash; } /** ** A keyed-hash message authentication code (HMAC) calculated using the secret key of a user pool client and * username plus the client ID in the message. *
* * @param secretHash * A keyed-hash message authentication code (HMAC) calculated using the secret key of a user pool client and * username plus the client ID in the message. * @return Returns a reference to this object so that method calls can be chained together. */ public SignUpRequest withSecretHash(String secretHash) { setSecretHash(secretHash); return this; } /** ** The user name of the user you want to register. *
* * @param username * The user name of the user you want to register. */ public void setUsername(String username) { this.username = username; } /** ** The user name of the user you want to register. *
* * @return The user name of the user you want to register. */ public String getUsername() { return this.username; } /** ** The user name of the user you want to register. *
* * @param username * The user name of the user you want to register. * @return Returns a reference to this object so that method calls can be chained together. */ public SignUpRequest withUsername(String username) { setUsername(username); return this; } /** ** The password of the user you want to register. *
* * @param password * The password of the user you want to register. */ public void setPassword(String password) { this.password = password; } /** ** The password of the user you want to register. *
* * @return The password of the user you want to register. */ public String getPassword() { return this.password; } /** ** The password of the user you want to register. *
* * @param password * The password of the user you want to register. * @return Returns a reference to this object so that method calls can be chained together. */ public SignUpRequest withPassword(String password) { setPassword(password); return this; } /** ** An array of name-value pairs representing user attributes. *
*
* For custom attributes, you must prepend the custom:
prefix to the attribute name.
*
* For custom attributes, you must prepend the
* An array of name-value pairs representing user attributes.
*
* For custom attributes, you must prepend the custom:
prefix to the attribute name.
*/
public java.util.Listcustom:
prefix to the attribute name.
*
* For custom attributes, you must prepend the
* An array of name-value pairs representing user attributes.
*
* For custom attributes, you must prepend the
* NOTE: This method appends the values to the existing list (if any). Use
* {@link #setUserAttributes(java.util.Collection)} or {@link #withUserAttributes(java.util.Collection)} if you want
* to override the existing values.
* custom:
prefix to the attribute name.
*/
public void setUserAttributes(java.util.Collectioncustom:
prefix to the attribute name.
*
* For custom attributes, you must prepend the
* An array of name-value pairs representing user attributes.
*
* For custom attributes, you must prepend the custom:
prefix to the attribute name.
* @return Returns a reference to this object so that method calls can be chained together.
*/
public SignUpRequest withUserAttributes(AttributeType... userAttributes) {
if (this.userAttributes == null) {
setUserAttributes(new java.util.ArrayListcustom:
prefix to the attribute name.
*
* For custom attributes, you must prepend the
* The validation data in the request to register a user.
*
* The validation data in the request to register a user.
*
* The validation data in the request to register a user.
*
* NOTE: This method appends the values to the existing list (if any). Use
* {@link #setValidationData(java.util.Collection)} or {@link #withValidationData(java.util.Collection)} if you want
* to override the existing values.
*
* The validation data in the request to register a user.
*
* The Amazon Pinpoint analytics metadata that contributes to your metrics for
* The Amazon Pinpoint analytics metadata that contributes to your metrics for
* The Amazon Pinpoint analytics metadata that contributes to your metrics for
* 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.
*
* 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.
*
* 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.
*
* A map of custom key-value pairs that you can provide as input for any custom workflows that this action triggers.
*
* You create custom workflows by assigning Lambda functions to user pool triggers. When you use the SignUp API
* action, Amazon Cognito invokes any functions that are assigned to the following triggers: pre sign-up,
* custom message, and post confirmation. When Amazon Cognito invokes any of these functions, it
* passes a JSON payload, which the function receives as input. This payload contains a
* 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.
* custom:
prefix to the attribute name.
* @return Returns a reference to this object so that method calls can be chained together.
*/
public SignUpRequest withUserAttributes(java.util.CollectionSignUp
calls.
* SignUp
calls.
*/
public void setAnalyticsMetadata(AnalyticsMetadataType analyticsMetadata) {
this.analyticsMetadata = analyticsMetadata;
}
/**
* SignUp
calls.
* SignUp
calls.
*/
public AnalyticsMetadataType getAnalyticsMetadata() {
return this.analyticsMetadata;
}
/**
* SignUp
calls.
* SignUp
calls.
* @return Returns a reference to this object so that method calls can be chained together.
*/
public SignUpRequest withAnalyticsMetadata(AnalyticsMetadataType analyticsMetadata) {
setAnalyticsMetadata(analyticsMetadata);
return this;
}
/**
* clientMetadata
* attribute, which provides the data that you assigned to the ClientMetadata parameter in your SignUp request. In
* your function code in Lambda, you can process the clientMetadata
value to enhance your workflow for
* your specific needs.
*
*
*
* You create custom workflows by assigning Lambda functions to user pool triggers. When you use the SignUp
* API action, Amazon Cognito invokes any functions that are assigned to the following triggers: pre
* sign-up, custom message, and post confirmation. When Amazon Cognito invokes any of
* these functions, it passes a JSON payload, which the function receives as input. This payload contains a
* clientMetadata
attribute, which provides the data that you assigned to the ClientMetadata
* parameter in your SignUp request. In your function code in Lambda, you can process the
* clientMetadata
value to enhance your workflow for your specific needs.
*
* For more information, see Customizing user pool Workflows with Lambda Triggers in the Amazon Cognito Developer Guide. *
** When you use the ClientMetadata parameter, remember that Amazon Cognito won't do the following: *
** Store the ClientMetadata value. This data is available only to Lambda triggers that are assigned to a * user pool to support custom workflows. If your user pool configuration doesn't include triggers, the * ClientMetadata parameter serves no purpose. *
** Validate the ClientMetadata value. *
** Encrypt the ClientMetadata value. Don't use Amazon Cognito to provide sensitive information. *
** A map of custom key-value pairs that you can provide as input for any custom workflows that this action triggers. *
*
* You create custom workflows by assigning Lambda functions to user pool triggers. When you use the SignUp API
* action, Amazon Cognito invokes any functions that are assigned to the following triggers: pre sign-up,
* custom message, and post confirmation. When Amazon Cognito invokes any of these functions, it
* passes a JSON payload, which the function receives as input. This payload contains a clientMetadata
* attribute, which provides the data that you assigned to the ClientMetadata parameter in your SignUp request. In
* your function code in Lambda, you can process the clientMetadata
value to enhance your workflow for
* your specific needs.
*
* For more information, see Customizing user pool Workflows with Lambda Triggers in the Amazon Cognito Developer Guide. *
** When you use the ClientMetadata parameter, remember that Amazon Cognito won't do the following: *
** Store the ClientMetadata value. This data is available only to Lambda triggers that are assigned to a user pool * to support custom workflows. If your user pool configuration doesn't include triggers, the ClientMetadata * parameter serves no purpose. *
** Validate the ClientMetadata value. *
** Encrypt the ClientMetadata value. Don't use Amazon Cognito to provide sensitive information. *
*
* You create custom workflows by assigning Lambda functions to user pool triggers. When you use the SignUp
* API action, Amazon Cognito invokes any functions that are assigned to the following triggers: pre
* sign-up, custom message, and post confirmation. When Amazon Cognito invokes any of these
* functions, it passes a JSON payload, which the function receives as input. This payload contains a
* clientMetadata
attribute, which provides the data that you assigned to the ClientMetadata
* parameter in your SignUp request. In your function code in Lambda, you can process the
* clientMetadata
value to enhance your workflow for your specific needs.
*
* For more information, see Customizing user pool Workflows with Lambda Triggers in the Amazon Cognito Developer Guide. *
** When you use the ClientMetadata parameter, remember that Amazon Cognito won't do the following: *
** Store the ClientMetadata value. This data is available only to Lambda triggers that are assigned to a user * pool to support custom workflows. If your user pool configuration doesn't include triggers, the * ClientMetadata parameter serves no purpose. *
** Validate the ClientMetadata value. *
** Encrypt the ClientMetadata value. Don't use Amazon Cognito to provide sensitive information. *
** A map of custom key-value pairs that you can provide as input for any custom workflows that this action triggers. *
*
* You create custom workflows by assigning Lambda functions to user pool triggers. When you use the SignUp API
* action, Amazon Cognito invokes any functions that are assigned to the following triggers: pre sign-up,
* custom message, and post confirmation. When Amazon Cognito invokes any of these functions, it
* passes a JSON payload, which the function receives as input. This payload contains a clientMetadata
* attribute, which provides the data that you assigned to the ClientMetadata parameter in your SignUp request. In
* your function code in Lambda, you can process the clientMetadata
value to enhance your workflow for
* your specific needs.
*
* For more information, see Customizing user pool Workflows with Lambda Triggers in the Amazon Cognito Developer Guide. *
** When you use the ClientMetadata parameter, remember that Amazon Cognito won't do the following: *
** Store the ClientMetadata value. This data is available only to Lambda triggers that are assigned to a user pool * to support custom workflows. If your user pool configuration doesn't include triggers, the ClientMetadata * parameter serves no purpose. *
** Validate the ClientMetadata value. *
** Encrypt the ClientMetadata value. Don't use Amazon Cognito to provide sensitive information. *
*
* You create custom workflows by assigning Lambda functions to user pool triggers. When you use the SignUp
* API action, Amazon Cognito invokes any functions that are assigned to the following triggers: pre
* sign-up, custom message, and post confirmation. When Amazon Cognito invokes any of these
* functions, it passes a JSON payload, which the function receives as input. This payload contains a
* clientMetadata
attribute, which provides the data that you assigned to the ClientMetadata
* parameter in your SignUp request. In your function code in Lambda, you can process the
* clientMetadata
value to enhance your workflow for your specific needs.
*
* For more information, see Customizing user pool Workflows with Lambda Triggers in the Amazon Cognito Developer Guide. *
** When you use the ClientMetadata parameter, remember that Amazon Cognito won't do the following: *
** Store the ClientMetadata value. This data is available only to Lambda triggers that are assigned to a user * pool to support custom workflows. If your user pool configuration doesn't include triggers, the * ClientMetadata parameter serves no purpose. *
** Validate the ClientMetadata value. *
** Encrypt the ClientMetadata value. Don't use Amazon Cognito to provide sensitive information. *
*