/**
* Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved.
* SPDX-License-Identifier: Apache-2.0.
*/
#pragma once
#include Represents the request to update the user's attributes as an
* administrator.See Also:
AWS
* API Reference
The user pool ID for the user pool where you want to update user * attributes.
*/ inline const Aws::String& GetUserPoolId() const{ return m_userPoolId; } /** *The user pool ID for the user pool where you want to update user * attributes.
*/ inline bool UserPoolIdHasBeenSet() const { return m_userPoolIdHasBeenSet; } /** *The user pool ID for the user pool where you want to update user * attributes.
*/ inline void SetUserPoolId(const Aws::String& value) { m_userPoolIdHasBeenSet = true; m_userPoolId = value; } /** *The user pool ID for the user pool where you want to update user * attributes.
*/ inline void SetUserPoolId(Aws::String&& value) { m_userPoolIdHasBeenSet = true; m_userPoolId = std::move(value); } /** *The user pool ID for the user pool where you want to update user * attributes.
*/ inline void SetUserPoolId(const char* value) { m_userPoolIdHasBeenSet = true; m_userPoolId.assign(value); } /** *The user pool ID for the user pool where you want to update user * attributes.
*/ inline AdminUpdateUserAttributesRequest& WithUserPoolId(const Aws::String& value) { SetUserPoolId(value); return *this;} /** *The user pool ID for the user pool where you want to update user * attributes.
*/ inline AdminUpdateUserAttributesRequest& WithUserPoolId(Aws::String&& value) { SetUserPoolId(std::move(value)); return *this;} /** *The user pool ID for the user pool where you want to update user * attributes.
*/ inline AdminUpdateUserAttributesRequest& WithUserPoolId(const char* value) { SetUserPoolId(value); return *this;} /** *The user name of the user for whom you want to update user attributes.
*/ inline const Aws::String& GetUsername() const{ return m_username; } /** *The user name of the user for whom you want to update user attributes.
*/ inline bool UsernameHasBeenSet() const { return m_usernameHasBeenSet; } /** *The user name of the user for whom you want to update user attributes.
*/ inline void SetUsername(const Aws::String& value) { m_usernameHasBeenSet = true; m_username = value; } /** *The user name of the user for whom you want to update user attributes.
*/ inline void SetUsername(Aws::String&& value) { m_usernameHasBeenSet = true; m_username = std::move(value); } /** *The user name of the user for whom you want to update user attributes.
*/ inline void SetUsername(const char* value) { m_usernameHasBeenSet = true; m_username.assign(value); } /** *The user name of the user for whom you want to update user attributes.
*/ inline AdminUpdateUserAttributesRequest& WithUsername(const Aws::String& value) { SetUsername(value); return *this;} /** *The user name of the user for whom you want to update user attributes.
*/ inline AdminUpdateUserAttributesRequest& WithUsername(Aws::String&& value) { SetUsername(std::move(value)); return *this;} /** *The user name of the user for whom you want to update user attributes.
*/ inline AdminUpdateUserAttributesRequest& WithUsername(const char* value) { SetUsername(value); return *this;} /** *An array of name-value pairs representing user attributes.
For custom
* attributes, you must prepend the custom: prefix to the attribute
* name.
An array of name-value pairs representing user attributes.
For custom
* attributes, you must prepend the custom: prefix to the attribute
* name.
An array of name-value pairs representing user attributes.
For custom
* attributes, you must prepend the custom: prefix to the attribute
* name.
An array of name-value pairs representing user attributes.
For custom
* attributes, you must prepend the custom: prefix to the attribute
* name.
An array of name-value pairs representing user attributes.
For custom
* attributes, you must prepend the custom: prefix to the attribute
* name.
An array of name-value pairs representing user attributes.
For custom
* attributes, you must prepend the custom: prefix to the attribute
* name.
An array of name-value pairs representing user attributes.
For custom
* attributes, you must prepend the custom: prefix to the attribute
* name.
An array of name-value pairs representing user attributes.
For custom
* attributes, you must prepend the custom: prefix to the attribute
* name.
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 AWS Lambda functions to user pool triggers. When you use the
* AdminUpdateUserAttributes API action, Amazon Cognito invokes the function that
* is assigned to the custom message trigger. When Amazon Cognito invokes
* this function, 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
* AdminUpdateUserAttributes request. In your function code in AWS 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.
Take the following limitations into consideration when * you use the ClientMetadata parameter:
Amazon Cognito does not * store the ClientMetadata value. This data is available only to AWS Lambda * triggers that are assigned to a user pool to support custom workflows. If your * user pool configuration does not include triggers, the ClientMetadata parameter * serves no purpose.
Amazon Cognito does not validate the * ClientMetadata value.
Amazon Cognito does not encrypt the the * ClientMetadata value, so don't use it to provide sensitive information.
*A map of custom key-value pairs that you can provide as input for any custom * workflows that this action triggers.
You create custom workflows by
* assigning AWS Lambda functions to user pool triggers. When you use the
* AdminUpdateUserAttributes API action, Amazon Cognito invokes the function that
* is assigned to the custom message trigger. When Amazon Cognito invokes
* this function, 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
* AdminUpdateUserAttributes request. In your function code in AWS 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.
Take the following limitations into consideration when * you use the ClientMetadata parameter:
Amazon Cognito does not * store the ClientMetadata value. This data is available only to AWS Lambda * triggers that are assigned to a user pool to support custom workflows. If your * user pool configuration does not include triggers, the ClientMetadata parameter * serves no purpose.
Amazon Cognito does not validate the * ClientMetadata value.
Amazon Cognito does not encrypt the the * ClientMetadata value, so don't use it to provide sensitive information.
*A map of custom key-value pairs that you can provide as input for any custom * workflows that this action triggers.
You create custom workflows by
* assigning AWS Lambda functions to user pool triggers. When you use the
* AdminUpdateUserAttributes API action, Amazon Cognito invokes the function that
* is assigned to the custom message trigger. When Amazon Cognito invokes
* this function, 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
* AdminUpdateUserAttributes request. In your function code in AWS 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.
Take the following limitations into consideration when * you use the ClientMetadata parameter:
Amazon Cognito does not * store the ClientMetadata value. This data is available only to AWS Lambda * triggers that are assigned to a user pool to support custom workflows. If your * user pool configuration does not include triggers, the ClientMetadata parameter * serves no purpose.
Amazon Cognito does not validate the * ClientMetadata value.
Amazon Cognito does not encrypt the the * ClientMetadata value, so don't use it to provide sensitive information.
*A map of custom key-value pairs that you can provide as input for any custom * workflows that this action triggers.
You create custom workflows by
* assigning AWS Lambda functions to user pool triggers. When you use the
* AdminUpdateUserAttributes API action, Amazon Cognito invokes the function that
* is assigned to the custom message trigger. When Amazon Cognito invokes
* this function, 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
* AdminUpdateUserAttributes request. In your function code in AWS 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.
Take the following limitations into consideration when * you use the ClientMetadata parameter:
Amazon Cognito does not * store the ClientMetadata value. This data is available only to AWS Lambda * triggers that are assigned to a user pool to support custom workflows. If your * user pool configuration does not include triggers, the ClientMetadata parameter * serves no purpose.
Amazon Cognito does not validate the * ClientMetadata value.
Amazon Cognito does not encrypt the the * ClientMetadata value, so don't use it to provide sensitive information.
*A map of custom key-value pairs that you can provide as input for any custom * workflows that this action triggers.
You create custom workflows by
* assigning AWS Lambda functions to user pool triggers. When you use the
* AdminUpdateUserAttributes API action, Amazon Cognito invokes the function that
* is assigned to the custom message trigger. When Amazon Cognito invokes
* this function, 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
* AdminUpdateUserAttributes request. In your function code in AWS 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.
Take the following limitations into consideration when * you use the ClientMetadata parameter:
Amazon Cognito does not * store the ClientMetadata value. This data is available only to AWS Lambda * triggers that are assigned to a user pool to support custom workflows. If your * user pool configuration does not include triggers, the ClientMetadata parameter * serves no purpose.
Amazon Cognito does not validate the * ClientMetadata value.
Amazon Cognito does not encrypt the the * ClientMetadata value, so don't use it to provide sensitive information.
*A map of custom key-value pairs that you can provide as input for any custom * workflows that this action triggers.
You create custom workflows by
* assigning AWS Lambda functions to user pool triggers. When you use the
* AdminUpdateUserAttributes API action, Amazon Cognito invokes the function that
* is assigned to the custom message trigger. When Amazon Cognito invokes
* this function, 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
* AdminUpdateUserAttributes request. In your function code in AWS 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.
Take the following limitations into consideration when * you use the ClientMetadata parameter:
Amazon Cognito does not * store the ClientMetadata value. This data is available only to AWS Lambda * triggers that are assigned to a user pool to support custom workflows. If your * user pool configuration does not include triggers, the ClientMetadata parameter * serves no purpose.
Amazon Cognito does not validate the * ClientMetadata value.
Amazon Cognito does not encrypt the the * ClientMetadata value, so don't use it to provide sensitive information.
*A map of custom key-value pairs that you can provide as input for any custom * workflows that this action triggers.
You create custom workflows by
* assigning AWS Lambda functions to user pool triggers. When you use the
* AdminUpdateUserAttributes API action, Amazon Cognito invokes the function that
* is assigned to the custom message trigger. When Amazon Cognito invokes
* this function, 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
* AdminUpdateUserAttributes request. In your function code in AWS 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.
Take the following limitations into consideration when * you use the ClientMetadata parameter:
Amazon Cognito does not * store the ClientMetadata value. This data is available only to AWS Lambda * triggers that are assigned to a user pool to support custom workflows. If your * user pool configuration does not include triggers, the ClientMetadata parameter * serves no purpose.
Amazon Cognito does not validate the * ClientMetadata value.
Amazon Cognito does not encrypt the the * ClientMetadata value, so don't use it to provide sensitive information.
*A map of custom key-value pairs that you can provide as input for any custom * workflows that this action triggers.
You create custom workflows by
* assigning AWS Lambda functions to user pool triggers. When you use the
* AdminUpdateUserAttributes API action, Amazon Cognito invokes the function that
* is assigned to the custom message trigger. When Amazon Cognito invokes
* this function, 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
* AdminUpdateUserAttributes request. In your function code in AWS 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.
Take the following limitations into consideration when * you use the ClientMetadata parameter:
Amazon Cognito does not * store the ClientMetadata value. This data is available only to AWS Lambda * triggers that are assigned to a user pool to support custom workflows. If your * user pool configuration does not include triggers, the ClientMetadata parameter * serves no purpose.
Amazon Cognito does not validate the * ClientMetadata value.
Amazon Cognito does not encrypt the the * ClientMetadata value, so don't use it to provide sensitive information.
*A map of custom key-value pairs that you can provide as input for any custom * workflows that this action triggers.
You create custom workflows by
* assigning AWS Lambda functions to user pool triggers. When you use the
* AdminUpdateUserAttributes API action, Amazon Cognito invokes the function that
* is assigned to the custom message trigger. When Amazon Cognito invokes
* this function, 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
* AdminUpdateUserAttributes request. In your function code in AWS 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.
Take the following limitations into consideration when * you use the ClientMetadata parameter:
Amazon Cognito does not * store the ClientMetadata value. This data is available only to AWS Lambda * triggers that are assigned to a user pool to support custom workflows. If your * user pool configuration does not include triggers, the ClientMetadata parameter * serves no purpose.
Amazon Cognito does not validate the * ClientMetadata value.
Amazon Cognito does not encrypt the the * ClientMetadata value, so don't use it to provide sensitive information.
*A map of custom key-value pairs that you can provide as input for any custom * workflows that this action triggers.
You create custom workflows by
* assigning AWS Lambda functions to user pool triggers. When you use the
* AdminUpdateUserAttributes API action, Amazon Cognito invokes the function that
* is assigned to the custom message trigger. When Amazon Cognito invokes
* this function, 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
* AdminUpdateUserAttributes request. In your function code in AWS 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.
Take the following limitations into consideration when * you use the ClientMetadata parameter:
Amazon Cognito does not * store the ClientMetadata value. This data is available only to AWS Lambda * triggers that are assigned to a user pool to support custom workflows. If your * user pool configuration does not include triggers, the ClientMetadata parameter * serves no purpose.
Amazon Cognito does not validate the * ClientMetadata value.
Amazon Cognito does not encrypt the the * ClientMetadata value, so don't use it to provide sensitive information.
*A map of custom key-value pairs that you can provide as input for any custom * workflows that this action triggers.
You create custom workflows by
* assigning AWS Lambda functions to user pool triggers. When you use the
* AdminUpdateUserAttributes API action, Amazon Cognito invokes the function that
* is assigned to the custom message trigger. When Amazon Cognito invokes
* this function, 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
* AdminUpdateUserAttributes request. In your function code in AWS 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.
Take the following limitations into consideration when * you use the ClientMetadata parameter:
Amazon Cognito does not * store the ClientMetadata value. This data is available only to AWS Lambda * triggers that are assigned to a user pool to support custom workflows. If your * user pool configuration does not include triggers, the ClientMetadata parameter * serves no purpose.
Amazon Cognito does not validate the * ClientMetadata value.
Amazon Cognito does not encrypt the the * ClientMetadata value, so don't use it to provide sensitive information.
*A map of custom key-value pairs that you can provide as input for any custom * workflows that this action triggers.
You create custom workflows by
* assigning AWS Lambda functions to user pool triggers. When you use the
* AdminUpdateUserAttributes API action, Amazon Cognito invokes the function that
* is assigned to the custom message trigger. When Amazon Cognito invokes
* this function, 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
* AdminUpdateUserAttributes request. In your function code in AWS 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.
Take the following limitations into consideration when * you use the ClientMetadata parameter:
Amazon Cognito does not * store the ClientMetadata value. This data is available only to AWS Lambda * triggers that are assigned to a user pool to support custom workflows. If your * user pool configuration does not include triggers, the ClientMetadata parameter * serves no purpose.
Amazon Cognito does not validate the * ClientMetadata value.
Amazon Cognito does not encrypt the the * ClientMetadata value, so don't use it to provide sensitive information.
*A map of custom key-value pairs that you can provide as input for any custom * workflows that this action triggers.
You create custom workflows by
* assigning AWS Lambda functions to user pool triggers. When you use the
* AdminUpdateUserAttributes API action, Amazon Cognito invokes the function that
* is assigned to the custom message trigger. When Amazon Cognito invokes
* this function, 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
* AdminUpdateUserAttributes request. In your function code in AWS 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.
Take the following limitations into consideration when * you use the ClientMetadata parameter:
Amazon Cognito does not * store the ClientMetadata value. This data is available only to AWS Lambda * triggers that are assigned to a user pool to support custom workflows. If your * user pool configuration does not include triggers, the ClientMetadata parameter * serves no purpose.
Amazon Cognito does not validate the * ClientMetadata value.
Amazon Cognito does not encrypt the the * ClientMetadata value, so don't use it to provide sensitive information.
*