This repository has been archived on 2025-09-14. You can view files and clone it, but cannot push or open issues or pull requests.
Files
pxz-hos-client-cpp-module/support/aws-sdk-cpp-master/aws-cpp-sdk-cognito-idp/include/aws/cognito-idp/model/SignUpRequest.h

766 lines
42 KiB
C
Raw Normal View History

/**
* Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved.
* SPDX-License-Identifier: Apache-2.0.
*/
#pragma once
#include <aws/cognito-idp/CognitoIdentityProvider_EXPORTS.h>
#include <aws/cognito-idp/CognitoIdentityProviderRequest.h>
#include <aws/core/utils/memory/stl/AWSString.h>
#include <aws/core/utils/memory/stl/AWSVector.h>
#include <aws/cognito-idp/model/AnalyticsMetadataType.h>
#include <aws/cognito-idp/model/UserContextDataType.h>
#include <aws/core/utils/memory/stl/AWSMap.h>
#include <aws/cognito-idp/model/AttributeType.h>
#include <utility>
namespace Aws
{
namespace CognitoIdentityProvider
{
namespace Model
{
/**
* <p>Represents the request to register a user.</p><p><h3>See Also:</h3> <a
* href="http://docs.aws.amazon.com/goto/WebAPI/cognito-idp-2016-04-18/SignUpRequest">AWS
* API Reference</a></p>
*/
class AWS_COGNITOIDENTITYPROVIDER_API SignUpRequest : public CognitoIdentityProviderRequest
{
public:
SignUpRequest();
// Service request name is the Operation name which will send this request out,
// each operation should has unique request name, so that we can get operation's name from this request.
// Note: this is not true for response, multiple operations may have the same response name,
// so we can not get operation's name from response.
inline virtual const char* GetServiceRequestName() const override { return "SignUp"; }
Aws::String SerializePayload() const override;
Aws::Http::HeaderValueCollection GetRequestSpecificHeaders() const override;
/**
* <p>The ID of the client associated with the user pool.</p>
*/
inline const Aws::String& GetClientId() const{ return m_clientId; }
/**
* <p>The ID of the client associated with the user pool.</p>
*/
inline bool ClientIdHasBeenSet() const { return m_clientIdHasBeenSet; }
/**
* <p>The ID of the client associated with the user pool.</p>
*/
inline void SetClientId(const Aws::String& value) { m_clientIdHasBeenSet = true; m_clientId = value; }
/**
* <p>The ID of the client associated with the user pool.</p>
*/
inline void SetClientId(Aws::String&& value) { m_clientIdHasBeenSet = true; m_clientId = std::move(value); }
/**
* <p>The ID of the client associated with the user pool.</p>
*/
inline void SetClientId(const char* value) { m_clientIdHasBeenSet = true; m_clientId.assign(value); }
/**
* <p>The ID of the client associated with the user pool.</p>
*/
inline SignUpRequest& WithClientId(const Aws::String& value) { SetClientId(value); return *this;}
/**
* <p>The ID of the client associated with the user pool.</p>
*/
inline SignUpRequest& WithClientId(Aws::String&& value) { SetClientId(std::move(value)); return *this;}
/**
* <p>The ID of the client associated with the user pool.</p>
*/
inline SignUpRequest& WithClientId(const char* value) { SetClientId(value); return *this;}
/**
* <p>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.</p>
*/
inline const Aws::String& GetSecretHash() const{ return m_secretHash; }
/**
* <p>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.</p>
*/
inline bool SecretHashHasBeenSet() const { return m_secretHashHasBeenSet; }
/**
* <p>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.</p>
*/
inline void SetSecretHash(const Aws::String& value) { m_secretHashHasBeenSet = true; m_secretHash = value; }
/**
* <p>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.</p>
*/
inline void SetSecretHash(Aws::String&& value) { m_secretHashHasBeenSet = true; m_secretHash = std::move(value); }
/**
* <p>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.</p>
*/
inline void SetSecretHash(const char* value) { m_secretHashHasBeenSet = true; m_secretHash.assign(value); }
/**
* <p>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.</p>
*/
inline SignUpRequest& WithSecretHash(const Aws::String& value) { SetSecretHash(value); return *this;}
/**
* <p>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.</p>
*/
inline SignUpRequest& WithSecretHash(Aws::String&& value) { SetSecretHash(std::move(value)); return *this;}
/**
* <p>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.</p>
*/
inline SignUpRequest& WithSecretHash(const char* value) { SetSecretHash(value); return *this;}
/**
* <p>The user name of the user you wish to register.</p>
*/
inline const Aws::String& GetUsername() const{ return m_username; }
/**
* <p>The user name of the user you wish to register.</p>
*/
inline bool UsernameHasBeenSet() const { return m_usernameHasBeenSet; }
/**
* <p>The user name of the user you wish to register.</p>
*/
inline void SetUsername(const Aws::String& value) { m_usernameHasBeenSet = true; m_username = value; }
/**
* <p>The user name of the user you wish to register.</p>
*/
inline void SetUsername(Aws::String&& value) { m_usernameHasBeenSet = true; m_username = std::move(value); }
/**
* <p>The user name of the user you wish to register.</p>
*/
inline void SetUsername(const char* value) { m_usernameHasBeenSet = true; m_username.assign(value); }
/**
* <p>The user name of the user you wish to register.</p>
*/
inline SignUpRequest& WithUsername(const Aws::String& value) { SetUsername(value); return *this;}
/**
* <p>The user name of the user you wish to register.</p>
*/
inline SignUpRequest& WithUsername(Aws::String&& value) { SetUsername(std::move(value)); return *this;}
/**
* <p>The user name of the user you wish to register.</p>
*/
inline SignUpRequest& WithUsername(const char* value) { SetUsername(value); return *this;}
/**
* <p>The password of the user you wish to register.</p>
*/
inline const Aws::String& GetPassword() const{ return m_password; }
/**
* <p>The password of the user you wish to register.</p>
*/
inline bool PasswordHasBeenSet() const { return m_passwordHasBeenSet; }
/**
* <p>The password of the user you wish to register.</p>
*/
inline void SetPassword(const Aws::String& value) { m_passwordHasBeenSet = true; m_password = value; }
/**
* <p>The password of the user you wish to register.</p>
*/
inline void SetPassword(Aws::String&& value) { m_passwordHasBeenSet = true; m_password = std::move(value); }
/**
* <p>The password of the user you wish to register.</p>
*/
inline void SetPassword(const char* value) { m_passwordHasBeenSet = true; m_password.assign(value); }
/**
* <p>The password of the user you wish to register.</p>
*/
inline SignUpRequest& WithPassword(const Aws::String& value) { SetPassword(value); return *this;}
/**
* <p>The password of the user you wish to register.</p>
*/
inline SignUpRequest& WithPassword(Aws::String&& value) { SetPassword(std::move(value)); return *this;}
/**
* <p>The password of the user you wish to register.</p>
*/
inline SignUpRequest& WithPassword(const char* value) { SetPassword(value); return *this;}
/**
* <p>An array of name-value pairs representing user attributes.</p> <p>For custom
* attributes, you must prepend the <code>custom:</code> prefix to the attribute
* name.</p>
*/
inline const Aws::Vector<AttributeType>& GetUserAttributes() const{ return m_userAttributes; }
/**
* <p>An array of name-value pairs representing user attributes.</p> <p>For custom
* attributes, you must prepend the <code>custom:</code> prefix to the attribute
* name.</p>
*/
inline bool UserAttributesHasBeenSet() const { return m_userAttributesHasBeenSet; }
/**
* <p>An array of name-value pairs representing user attributes.</p> <p>For custom
* attributes, you must prepend the <code>custom:</code> prefix to the attribute
* name.</p>
*/
inline void SetUserAttributes(const Aws::Vector<AttributeType>& value) { m_userAttributesHasBeenSet = true; m_userAttributes = value; }
/**
* <p>An array of name-value pairs representing user attributes.</p> <p>For custom
* attributes, you must prepend the <code>custom:</code> prefix to the attribute
* name.</p>
*/
inline void SetUserAttributes(Aws::Vector<AttributeType>&& value) { m_userAttributesHasBeenSet = true; m_userAttributes = std::move(value); }
/**
* <p>An array of name-value pairs representing user attributes.</p> <p>For custom
* attributes, you must prepend the <code>custom:</code> prefix to the attribute
* name.</p>
*/
inline SignUpRequest& WithUserAttributes(const Aws::Vector<AttributeType>& value) { SetUserAttributes(value); return *this;}
/**
* <p>An array of name-value pairs representing user attributes.</p> <p>For custom
* attributes, you must prepend the <code>custom:</code> prefix to the attribute
* name.</p>
*/
inline SignUpRequest& WithUserAttributes(Aws::Vector<AttributeType>&& value) { SetUserAttributes(std::move(value)); return *this;}
/**
* <p>An array of name-value pairs representing user attributes.</p> <p>For custom
* attributes, you must prepend the <code>custom:</code> prefix to the attribute
* name.</p>
*/
inline SignUpRequest& AddUserAttributes(const AttributeType& value) { m_userAttributesHasBeenSet = true; m_userAttributes.push_back(value); return *this; }
/**
* <p>An array of name-value pairs representing user attributes.</p> <p>For custom
* attributes, you must prepend the <code>custom:</code> prefix to the attribute
* name.</p>
*/
inline SignUpRequest& AddUserAttributes(AttributeType&& value) { m_userAttributesHasBeenSet = true; m_userAttributes.push_back(std::move(value)); return *this; }
/**
* <p>The validation data in the request to register a user.</p>
*/
inline const Aws::Vector<AttributeType>& GetValidationData() const{ return m_validationData; }
/**
* <p>The validation data in the request to register a user.</p>
*/
inline bool ValidationDataHasBeenSet() const { return m_validationDataHasBeenSet; }
/**
* <p>The validation data in the request to register a user.</p>
*/
inline void SetValidationData(const Aws::Vector<AttributeType>& value) { m_validationDataHasBeenSet = true; m_validationData = value; }
/**
* <p>The validation data in the request to register a user.</p>
*/
inline void SetValidationData(Aws::Vector<AttributeType>&& value) { m_validationDataHasBeenSet = true; m_validationData = std::move(value); }
/**
* <p>The validation data in the request to register a user.</p>
*/
inline SignUpRequest& WithValidationData(const Aws::Vector<AttributeType>& value) { SetValidationData(value); return *this;}
/**
* <p>The validation data in the request to register a user.</p>
*/
inline SignUpRequest& WithValidationData(Aws::Vector<AttributeType>&& value) { SetValidationData(std::move(value)); return *this;}
/**
* <p>The validation data in the request to register a user.</p>
*/
inline SignUpRequest& AddValidationData(const AttributeType& value) { m_validationDataHasBeenSet = true; m_validationData.push_back(value); return *this; }
/**
* <p>The validation data in the request to register a user.</p>
*/
inline SignUpRequest& AddValidationData(AttributeType&& value) { m_validationDataHasBeenSet = true; m_validationData.push_back(std::move(value)); return *this; }
/**
* <p>The Amazon Pinpoint analytics metadata for collecting metrics for
* <code>SignUp</code> calls.</p>
*/
inline const AnalyticsMetadataType& GetAnalyticsMetadata() const{ return m_analyticsMetadata; }
/**
* <p>The Amazon Pinpoint analytics metadata for collecting metrics for
* <code>SignUp</code> calls.</p>
*/
inline bool AnalyticsMetadataHasBeenSet() const { return m_analyticsMetadataHasBeenSet; }
/**
* <p>The Amazon Pinpoint analytics metadata for collecting metrics for
* <code>SignUp</code> calls.</p>
*/
inline void SetAnalyticsMetadata(const AnalyticsMetadataType& value) { m_analyticsMetadataHasBeenSet = true; m_analyticsMetadata = value; }
/**
* <p>The Amazon Pinpoint analytics metadata for collecting metrics for
* <code>SignUp</code> calls.</p>
*/
inline void SetAnalyticsMetadata(AnalyticsMetadataType&& value) { m_analyticsMetadataHasBeenSet = true; m_analyticsMetadata = std::move(value); }
/**
* <p>The Amazon Pinpoint analytics metadata for collecting metrics for
* <code>SignUp</code> calls.</p>
*/
inline SignUpRequest& WithAnalyticsMetadata(const AnalyticsMetadataType& value) { SetAnalyticsMetadata(value); return *this;}
/**
* <p>The Amazon Pinpoint analytics metadata for collecting metrics for
* <code>SignUp</code> calls.</p>
*/
inline SignUpRequest& WithAnalyticsMetadata(AnalyticsMetadataType&& value) { SetAnalyticsMetadata(std::move(value)); return *this;}
/**
* <p>Contextual data such as the user's device fingerprint, IP address, or
* location used for evaluating the risk of an unexpected event by Amazon Cognito
* advanced security.</p>
*/
inline const UserContextDataType& GetUserContextData() const{ return m_userContextData; }
/**
* <p>Contextual data such as the user's device fingerprint, IP address, or
* location used for evaluating the risk of an unexpected event by Amazon Cognito
* advanced security.</p>
*/
inline bool UserContextDataHasBeenSet() const { return m_userContextDataHasBeenSet; }
/**
* <p>Contextual data such as the user's device fingerprint, IP address, or
* location used for evaluating the risk of an unexpected event by Amazon Cognito
* advanced security.</p>
*/
inline void SetUserContextData(const UserContextDataType& value) { m_userContextDataHasBeenSet = true; m_userContextData = value; }
/**
* <p>Contextual data such as the user's device fingerprint, IP address, or
* location used for evaluating the risk of an unexpected event by Amazon Cognito
* advanced security.</p>
*/
inline void SetUserContextData(UserContextDataType&& value) { m_userContextDataHasBeenSet = true; m_userContextData = std::move(value); }
/**
* <p>Contextual data such as the user's device fingerprint, IP address, or
* location used for evaluating the risk of an unexpected event by Amazon Cognito
* advanced security.</p>
*/
inline SignUpRequest& WithUserContextData(const UserContextDataType& value) { SetUserContextData(value); return *this;}
/**
* <p>Contextual data such as the user's device fingerprint, IP address, or
* location used for evaluating the risk of an unexpected event by Amazon Cognito
* advanced security.</p>
*/
inline SignUpRequest& WithUserContextData(UserContextDataType&& value) { SetUserContextData(std::move(value)); return *this;}
/**
* <p>A map of custom key-value pairs that you can provide as input for any custom
* workflows that this action triggers. </p> <p>You create custom workflows by
* assigning AWS 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: <i>pre sign-up</i>, <i>custom message</i>, and <i>post
* confirmation</i>. When Amazon Cognito invokes any of these functions, it passes
* a JSON payload, which the function receives as input. This payload contains a
* <code>clientMetadata</code> attribute, which provides the data that you assigned
* to the ClientMetadata parameter in your SignUp request. In your function code in
* AWS Lambda, you can process the <code>clientMetadata</code> value to enhance
* your workflow for your specific needs.</p> <p>For more information, see <a
* href="https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-identity-pools-working-with-aws-lambda-triggers.html">Customizing
* User Pool Workflows with Lambda Triggers</a> in the <i>Amazon Cognito Developer
* Guide</i>.</p> <p>Take the following limitations into consideration when
* you use the ClientMetadata parameter:</p> <ul> <li> <p>Amazon Cognito does not
* store the ClientMetadata value. This data is available only to AWS Lambda
* triggers that are assigned to a user pool to support custom workflows. If your
* user pool configuration does not include triggers, the ClientMetadata parameter
* serves no purpose.</p> </li> <li> <p>Amazon Cognito does not validate the
* ClientMetadata value.</p> </li> <li> <p>Amazon Cognito does not encrypt the the
* ClientMetadata value, so don't use it to provide sensitive information.</p>
* </li> </ul>
*/
inline const Aws::Map<Aws::String, Aws::String>& GetClientMetadata() const{ return m_clientMetadata; }
/**
* <p>A map of custom key-value pairs that you can provide as input for any custom
* workflows that this action triggers. </p> <p>You create custom workflows by
* assigning AWS 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: <i>pre sign-up</i>, <i>custom message</i>, and <i>post
* confirmation</i>. When Amazon Cognito invokes any of these functions, it passes
* a JSON payload, which the function receives as input. This payload contains a
* <code>clientMetadata</code> attribute, which provides the data that you assigned
* to the ClientMetadata parameter in your SignUp request. In your function code in
* AWS Lambda, you can process the <code>clientMetadata</code> value to enhance
* your workflow for your specific needs.</p> <p>For more information, see <a
* href="https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-identity-pools-working-with-aws-lambda-triggers.html">Customizing
* User Pool Workflows with Lambda Triggers</a> in the <i>Amazon Cognito Developer
* Guide</i>.</p> <p>Take the following limitations into consideration when
* you use the ClientMetadata parameter:</p> <ul> <li> <p>Amazon Cognito does not
* store the ClientMetadata value. This data is available only to AWS Lambda
* triggers that are assigned to a user pool to support custom workflows. If your
* user pool configuration does not include triggers, the ClientMetadata parameter
* serves no purpose.</p> </li> <li> <p>Amazon Cognito does not validate the
* ClientMetadata value.</p> </li> <li> <p>Amazon Cognito does not encrypt the the
* ClientMetadata value, so don't use it to provide sensitive information.</p>
* </li> </ul>
*/
inline bool ClientMetadataHasBeenSet() const { return m_clientMetadataHasBeenSet; }
/**
* <p>A map of custom key-value pairs that you can provide as input for any custom
* workflows that this action triggers. </p> <p>You create custom workflows by
* assigning AWS 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: <i>pre sign-up</i>, <i>custom message</i>, and <i>post
* confirmation</i>. When Amazon Cognito invokes any of these functions, it passes
* a JSON payload, which the function receives as input. This payload contains a
* <code>clientMetadata</code> attribute, which provides the data that you assigned
* to the ClientMetadata parameter in your SignUp request. In your function code in
* AWS Lambda, you can process the <code>clientMetadata</code> value to enhance
* your workflow for your specific needs.</p> <p>For more information, see <a
* href="https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-identity-pools-working-with-aws-lambda-triggers.html">Customizing
* User Pool Workflows with Lambda Triggers</a> in the <i>Amazon Cognito Developer
* Guide</i>.</p> <p>Take the following limitations into consideration when
* you use the ClientMetadata parameter:</p> <ul> <li> <p>Amazon Cognito does not
* store the ClientMetadata value. This data is available only to AWS Lambda
* triggers that are assigned to a user pool to support custom workflows. If your
* user pool configuration does not include triggers, the ClientMetadata parameter
* serves no purpose.</p> </li> <li> <p>Amazon Cognito does not validate the
* ClientMetadata value.</p> </li> <li> <p>Amazon Cognito does not encrypt the the
* ClientMetadata value, so don't use it to provide sensitive information.</p>
* </li> </ul>
*/
inline void SetClientMetadata(const Aws::Map<Aws::String, Aws::String>& value) { m_clientMetadataHasBeenSet = true; m_clientMetadata = value; }
/**
* <p>A map of custom key-value pairs that you can provide as input for any custom
* workflows that this action triggers. </p> <p>You create custom workflows by
* assigning AWS 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: <i>pre sign-up</i>, <i>custom message</i>, and <i>post
* confirmation</i>. When Amazon Cognito invokes any of these functions, it passes
* a JSON payload, which the function receives as input. This payload contains a
* <code>clientMetadata</code> attribute, which provides the data that you assigned
* to the ClientMetadata parameter in your SignUp request. In your function code in
* AWS Lambda, you can process the <code>clientMetadata</code> value to enhance
* your workflow for your specific needs.</p> <p>For more information, see <a
* href="https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-identity-pools-working-with-aws-lambda-triggers.html">Customizing
* User Pool Workflows with Lambda Triggers</a> in the <i>Amazon Cognito Developer
* Guide</i>.</p> <p>Take the following limitations into consideration when
* you use the ClientMetadata parameter:</p> <ul> <li> <p>Amazon Cognito does not
* store the ClientMetadata value. This data is available only to AWS Lambda
* triggers that are assigned to a user pool to support custom workflows. If your
* user pool configuration does not include triggers, the ClientMetadata parameter
* serves no purpose.</p> </li> <li> <p>Amazon Cognito does not validate the
* ClientMetadata value.</p> </li> <li> <p>Amazon Cognito does not encrypt the the
* ClientMetadata value, so don't use it to provide sensitive information.</p>
* </li> </ul>
*/
inline void SetClientMetadata(Aws::Map<Aws::String, Aws::String>&& value) { m_clientMetadataHasBeenSet = true; m_clientMetadata = std::move(value); }
/**
* <p>A map of custom key-value pairs that you can provide as input for any custom
* workflows that this action triggers. </p> <p>You create custom workflows by
* assigning AWS 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: <i>pre sign-up</i>, <i>custom message</i>, and <i>post
* confirmation</i>. When Amazon Cognito invokes any of these functions, it passes
* a JSON payload, which the function receives as input. This payload contains a
* <code>clientMetadata</code> attribute, which provides the data that you assigned
* to the ClientMetadata parameter in your SignUp request. In your function code in
* AWS Lambda, you can process the <code>clientMetadata</code> value to enhance
* your workflow for your specific needs.</p> <p>For more information, see <a
* href="https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-identity-pools-working-with-aws-lambda-triggers.html">Customizing
* User Pool Workflows with Lambda Triggers</a> in the <i>Amazon Cognito Developer
* Guide</i>.</p> <p>Take the following limitations into consideration when
* you use the ClientMetadata parameter:</p> <ul> <li> <p>Amazon Cognito does not
* store the ClientMetadata value. This data is available only to AWS Lambda
* triggers that are assigned to a user pool to support custom workflows. If your
* user pool configuration does not include triggers, the ClientMetadata parameter
* serves no purpose.</p> </li> <li> <p>Amazon Cognito does not validate the
* ClientMetadata value.</p> </li> <li> <p>Amazon Cognito does not encrypt the the
* ClientMetadata value, so don't use it to provide sensitive information.</p>
* </li> </ul>
*/
inline SignUpRequest& WithClientMetadata(const Aws::Map<Aws::String, Aws::String>& value) { SetClientMetadata(value); return *this;}
/**
* <p>A map of custom key-value pairs that you can provide as input for any custom
* workflows that this action triggers. </p> <p>You create custom workflows by
* assigning AWS 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: <i>pre sign-up</i>, <i>custom message</i>, and <i>post
* confirmation</i>. When Amazon Cognito invokes any of these functions, it passes
* a JSON payload, which the function receives as input. This payload contains a
* <code>clientMetadata</code> attribute, which provides the data that you assigned
* to the ClientMetadata parameter in your SignUp request. In your function code in
* AWS Lambda, you can process the <code>clientMetadata</code> value to enhance
* your workflow for your specific needs.</p> <p>For more information, see <a
* href="https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-identity-pools-working-with-aws-lambda-triggers.html">Customizing
* User Pool Workflows with Lambda Triggers</a> in the <i>Amazon Cognito Developer
* Guide</i>.</p> <p>Take the following limitations into consideration when
* you use the ClientMetadata parameter:</p> <ul> <li> <p>Amazon Cognito does not
* store the ClientMetadata value. This data is available only to AWS Lambda
* triggers that are assigned to a user pool to support custom workflows. If your
* user pool configuration does not include triggers, the ClientMetadata parameter
* serves no purpose.</p> </li> <li> <p>Amazon Cognito does not validate the
* ClientMetadata value.</p> </li> <li> <p>Amazon Cognito does not encrypt the the
* ClientMetadata value, so don't use it to provide sensitive information.</p>
* </li> </ul>
*/
inline SignUpRequest& WithClientMetadata(Aws::Map<Aws::String, Aws::String>&& value) { SetClientMetadata(std::move(value)); return *this;}
/**
* <p>A map of custom key-value pairs that you can provide as input for any custom
* workflows that this action triggers. </p> <p>You create custom workflows by
* assigning AWS 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: <i>pre sign-up</i>, <i>custom message</i>, and <i>post
* confirmation</i>. When Amazon Cognito invokes any of these functions, it passes
* a JSON payload, which the function receives as input. This payload contains a
* <code>clientMetadata</code> attribute, which provides the data that you assigned
* to the ClientMetadata parameter in your SignUp request. In your function code in
* AWS Lambda, you can process the <code>clientMetadata</code> value to enhance
* your workflow for your specific needs.</p> <p>For more information, see <a
* href="https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-identity-pools-working-with-aws-lambda-triggers.html">Customizing
* User Pool Workflows with Lambda Triggers</a> in the <i>Amazon Cognito Developer
* Guide</i>.</p> <p>Take the following limitations into consideration when
* you use the ClientMetadata parameter:</p> <ul> <li> <p>Amazon Cognito does not
* store the ClientMetadata value. This data is available only to AWS Lambda
* triggers that are assigned to a user pool to support custom workflows. If your
* user pool configuration does not include triggers, the ClientMetadata parameter
* serves no purpose.</p> </li> <li> <p>Amazon Cognito does not validate the
* ClientMetadata value.</p> </li> <li> <p>Amazon Cognito does not encrypt the the
* ClientMetadata value, so don't use it to provide sensitive information.</p>
* </li> </ul>
*/
inline SignUpRequest& AddClientMetadata(const Aws::String& key, const Aws::String& value) { m_clientMetadataHasBeenSet = true; m_clientMetadata.emplace(key, value); return *this; }
/**
* <p>A map of custom key-value pairs that you can provide as input for any custom
* workflows that this action triggers. </p> <p>You create custom workflows by
* assigning AWS 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: <i>pre sign-up</i>, <i>custom message</i>, and <i>post
* confirmation</i>. When Amazon Cognito invokes any of these functions, it passes
* a JSON payload, which the function receives as input. This payload contains a
* <code>clientMetadata</code> attribute, which provides the data that you assigned
* to the ClientMetadata parameter in your SignUp request. In your function code in
* AWS Lambda, you can process the <code>clientMetadata</code> value to enhance
* your workflow for your specific needs.</p> <p>For more information, see <a
* href="https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-identity-pools-working-with-aws-lambda-triggers.html">Customizing
* User Pool Workflows with Lambda Triggers</a> in the <i>Amazon Cognito Developer
* Guide</i>.</p> <p>Take the following limitations into consideration when
* you use the ClientMetadata parameter:</p> <ul> <li> <p>Amazon Cognito does not
* store the ClientMetadata value. This data is available only to AWS Lambda
* triggers that are assigned to a user pool to support custom workflows. If your
* user pool configuration does not include triggers, the ClientMetadata parameter
* serves no purpose.</p> </li> <li> <p>Amazon Cognito does not validate the
* ClientMetadata value.</p> </li> <li> <p>Amazon Cognito does not encrypt the the
* ClientMetadata value, so don't use it to provide sensitive information.</p>
* </li> </ul>
*/
inline SignUpRequest& AddClientMetadata(Aws::String&& key, const Aws::String& value) { m_clientMetadataHasBeenSet = true; m_clientMetadata.emplace(std::move(key), value); return *this; }
/**
* <p>A map of custom key-value pairs that you can provide as input for any custom
* workflows that this action triggers. </p> <p>You create custom workflows by
* assigning AWS 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: <i>pre sign-up</i>, <i>custom message</i>, and <i>post
* confirmation</i>. When Amazon Cognito invokes any of these functions, it passes
* a JSON payload, which the function receives as input. This payload contains a
* <code>clientMetadata</code> attribute, which provides the data that you assigned
* to the ClientMetadata parameter in your SignUp request. In your function code in
* AWS Lambda, you can process the <code>clientMetadata</code> value to enhance
* your workflow for your specific needs.</p> <p>For more information, see <a
* href="https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-identity-pools-working-with-aws-lambda-triggers.html">Customizing
* User Pool Workflows with Lambda Triggers</a> in the <i>Amazon Cognito Developer
* Guide</i>.</p> <p>Take the following limitations into consideration when
* you use the ClientMetadata parameter:</p> <ul> <li> <p>Amazon Cognito does not
* store the ClientMetadata value. This data is available only to AWS Lambda
* triggers that are assigned to a user pool to support custom workflows. If your
* user pool configuration does not include triggers, the ClientMetadata parameter
* serves no purpose.</p> </li> <li> <p>Amazon Cognito does not validate the
* ClientMetadata value.</p> </li> <li> <p>Amazon Cognito does not encrypt the the
* ClientMetadata value, so don't use it to provide sensitive information.</p>
* </li> </ul>
*/
inline SignUpRequest& AddClientMetadata(const Aws::String& key, Aws::String&& value) { m_clientMetadataHasBeenSet = true; m_clientMetadata.emplace(key, std::move(value)); return *this; }
/**
* <p>A map of custom key-value pairs that you can provide as input for any custom
* workflows that this action triggers. </p> <p>You create custom workflows by
* assigning AWS 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: <i>pre sign-up</i>, <i>custom message</i>, and <i>post
* confirmation</i>. When Amazon Cognito invokes any of these functions, it passes
* a JSON payload, which the function receives as input. This payload contains a
* <code>clientMetadata</code> attribute, which provides the data that you assigned
* to the ClientMetadata parameter in your SignUp request. In your function code in
* AWS Lambda, you can process the <code>clientMetadata</code> value to enhance
* your workflow for your specific needs.</p> <p>For more information, see <a
* href="https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-identity-pools-working-with-aws-lambda-triggers.html">Customizing
* User Pool Workflows with Lambda Triggers</a> in the <i>Amazon Cognito Developer
* Guide</i>.</p> <p>Take the following limitations into consideration when
* you use the ClientMetadata parameter:</p> <ul> <li> <p>Amazon Cognito does not
* store the ClientMetadata value. This data is available only to AWS Lambda
* triggers that are assigned to a user pool to support custom workflows. If your
* user pool configuration does not include triggers, the ClientMetadata parameter
* serves no purpose.</p> </li> <li> <p>Amazon Cognito does not validate the
* ClientMetadata value.</p> </li> <li> <p>Amazon Cognito does not encrypt the the
* ClientMetadata value, so don't use it to provide sensitive information.</p>
* </li> </ul>
*/
inline SignUpRequest& AddClientMetadata(Aws::String&& key, Aws::String&& value) { m_clientMetadataHasBeenSet = true; m_clientMetadata.emplace(std::move(key), std::move(value)); return *this; }
/**
* <p>A map of custom key-value pairs that you can provide as input for any custom
* workflows that this action triggers. </p> <p>You create custom workflows by
* assigning AWS 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: <i>pre sign-up</i>, <i>custom message</i>, and <i>post
* confirmation</i>. When Amazon Cognito invokes any of these functions, it passes
* a JSON payload, which the function receives as input. This payload contains a
* <code>clientMetadata</code> attribute, which provides the data that you assigned
* to the ClientMetadata parameter in your SignUp request. In your function code in
* AWS Lambda, you can process the <code>clientMetadata</code> value to enhance
* your workflow for your specific needs.</p> <p>For more information, see <a
* href="https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-identity-pools-working-with-aws-lambda-triggers.html">Customizing
* User Pool Workflows with Lambda Triggers</a> in the <i>Amazon Cognito Developer
* Guide</i>.</p> <p>Take the following limitations into consideration when
* you use the ClientMetadata parameter:</p> <ul> <li> <p>Amazon Cognito does not
* store the ClientMetadata value. This data is available only to AWS Lambda
* triggers that are assigned to a user pool to support custom workflows. If your
* user pool configuration does not include triggers, the ClientMetadata parameter
* serves no purpose.</p> </li> <li> <p>Amazon Cognito does not validate the
* ClientMetadata value.</p> </li> <li> <p>Amazon Cognito does not encrypt the the
* ClientMetadata value, so don't use it to provide sensitive information.</p>
* </li> </ul>
*/
inline SignUpRequest& AddClientMetadata(const char* key, Aws::String&& value) { m_clientMetadataHasBeenSet = true; m_clientMetadata.emplace(key, std::move(value)); return *this; }
/**
* <p>A map of custom key-value pairs that you can provide as input for any custom
* workflows that this action triggers. </p> <p>You create custom workflows by
* assigning AWS 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: <i>pre sign-up</i>, <i>custom message</i>, and <i>post
* confirmation</i>. When Amazon Cognito invokes any of these functions, it passes
* a JSON payload, which the function receives as input. This payload contains a
* <code>clientMetadata</code> attribute, which provides the data that you assigned
* to the ClientMetadata parameter in your SignUp request. In your function code in
* AWS Lambda, you can process the <code>clientMetadata</code> value to enhance
* your workflow for your specific needs.</p> <p>For more information, see <a
* href="https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-identity-pools-working-with-aws-lambda-triggers.html">Customizing
* User Pool Workflows with Lambda Triggers</a> in the <i>Amazon Cognito Developer
* Guide</i>.</p> <p>Take the following limitations into consideration when
* you use the ClientMetadata parameter:</p> <ul> <li> <p>Amazon Cognito does not
* store the ClientMetadata value. This data is available only to AWS Lambda
* triggers that are assigned to a user pool to support custom workflows. If your
* user pool configuration does not include triggers, the ClientMetadata parameter
* serves no purpose.</p> </li> <li> <p>Amazon Cognito does not validate the
* ClientMetadata value.</p> </li> <li> <p>Amazon Cognito does not encrypt the the
* ClientMetadata value, so don't use it to provide sensitive information.</p>
* </li> </ul>
*/
inline SignUpRequest& AddClientMetadata(Aws::String&& key, const char* value) { m_clientMetadataHasBeenSet = true; m_clientMetadata.emplace(std::move(key), value); return *this; }
/**
* <p>A map of custom key-value pairs that you can provide as input for any custom
* workflows that this action triggers. </p> <p>You create custom workflows by
* assigning AWS 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: <i>pre sign-up</i>, <i>custom message</i>, and <i>post
* confirmation</i>. When Amazon Cognito invokes any of these functions, it passes
* a JSON payload, which the function receives as input. This payload contains a
* <code>clientMetadata</code> attribute, which provides the data that you assigned
* to the ClientMetadata parameter in your SignUp request. In your function code in
* AWS Lambda, you can process the <code>clientMetadata</code> value to enhance
* your workflow for your specific needs.</p> <p>For more information, see <a
* href="https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-identity-pools-working-with-aws-lambda-triggers.html">Customizing
* User Pool Workflows with Lambda Triggers</a> in the <i>Amazon Cognito Developer
* Guide</i>.</p> <p>Take the following limitations into consideration when
* you use the ClientMetadata parameter:</p> <ul> <li> <p>Amazon Cognito does not
* store the ClientMetadata value. This data is available only to AWS Lambda
* triggers that are assigned to a user pool to support custom workflows. If your
* user pool configuration does not include triggers, the ClientMetadata parameter
* serves no purpose.</p> </li> <li> <p>Amazon Cognito does not validate the
* ClientMetadata value.</p> </li> <li> <p>Amazon Cognito does not encrypt the the
* ClientMetadata value, so don't use it to provide sensitive information.</p>
* </li> </ul>
*/
inline SignUpRequest& AddClientMetadata(const char* key, const char* value) { m_clientMetadataHasBeenSet = true; m_clientMetadata.emplace(key, value); return *this; }
private:
Aws::String m_clientId;
bool m_clientIdHasBeenSet;
Aws::String m_secretHash;
bool m_secretHashHasBeenSet;
Aws::String m_username;
bool m_usernameHasBeenSet;
Aws::String m_password;
bool m_passwordHasBeenSet;
Aws::Vector<AttributeType> m_userAttributes;
bool m_userAttributesHasBeenSet;
Aws::Vector<AttributeType> m_validationData;
bool m_validationDataHasBeenSet;
AnalyticsMetadataType m_analyticsMetadata;
bool m_analyticsMetadataHasBeenSet;
UserContextDataType m_userContextData;
bool m_userContextDataHasBeenSet;
Aws::Map<Aws::String, Aws::String> m_clientMetadata;
bool m_clientMetadataHasBeenSet;
};
} // namespace Model
} // namespace CognitoIdentityProvider
} // namespace Aws