/** * Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved. * SPDX-License-Identifier: Apache-2.0. */ #pragma once #include #include #include #include #include #include #include namespace Aws { namespace CognitoIdentityProvider { namespace Model { /** *

Represents the request to update user attributes.

See Also:

* AWS * API Reference

*/ class AWS_COGNITOIDENTITYPROVIDER_API UpdateUserAttributesRequest : public CognitoIdentityProviderRequest { public: UpdateUserAttributesRequest(); // 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 "UpdateUserAttributes"; } Aws::String SerializePayload() const override; Aws::Http::HeaderValueCollection GetRequestSpecificHeaders() const override; /** *

An array of name-value pairs representing user attributes.

For custom * attributes, you must prepend the custom: prefix to the attribute * name.

*/ inline const Aws::Vector& GetUserAttributes() const{ return m_userAttributes; } /** *

An array of name-value pairs representing user attributes.

For custom * attributes, you must prepend the custom: prefix to the attribute * name.

*/ inline bool UserAttributesHasBeenSet() const { return m_userAttributesHasBeenSet; } /** *

An array of name-value pairs representing user attributes.

For custom * attributes, you must prepend the custom: prefix to the attribute * name.

*/ inline void SetUserAttributes(const Aws::Vector& value) { m_userAttributesHasBeenSet = true; m_userAttributes = value; } /** *

An array of name-value pairs representing user attributes.

For custom * attributes, you must prepend the custom: prefix to the attribute * name.

*/ inline void SetUserAttributes(Aws::Vector&& value) { m_userAttributesHasBeenSet = true; m_userAttributes = std::move(value); } /** *

An array of name-value pairs representing user attributes.

For custom * attributes, you must prepend the custom: prefix to the attribute * name.

*/ inline UpdateUserAttributesRequest& WithUserAttributes(const Aws::Vector& value) { SetUserAttributes(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.

*/ inline UpdateUserAttributesRequest& WithUserAttributes(Aws::Vector&& value) { SetUserAttributes(std::move(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.

*/ inline UpdateUserAttributesRequest& AddUserAttributes(const AttributeType& value) { m_userAttributesHasBeenSet = true; m_userAttributes.push_back(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.

*/ inline UpdateUserAttributesRequest& AddUserAttributes(AttributeType&& value) { m_userAttributesHasBeenSet = true; m_userAttributes.push_back(std::move(value)); return *this; } /** *

The access token for the request to update user attributes.

*/ inline const Aws::String& GetAccessToken() const{ return m_accessToken; } /** *

The access token for the request to update user attributes.

*/ inline bool AccessTokenHasBeenSet() const { return m_accessTokenHasBeenSet; } /** *

The access token for the request to update user attributes.

*/ inline void SetAccessToken(const Aws::String& value) { m_accessTokenHasBeenSet = true; m_accessToken = value; } /** *

The access token for the request to update user attributes.

*/ inline void SetAccessToken(Aws::String&& value) { m_accessTokenHasBeenSet = true; m_accessToken = std::move(value); } /** *

The access token for the request to update user attributes.

*/ inline void SetAccessToken(const char* value) { m_accessTokenHasBeenSet = true; m_accessToken.assign(value); } /** *

The access token for the request to update user attributes.

*/ inline UpdateUserAttributesRequest& WithAccessToken(const Aws::String& value) { SetAccessToken(value); return *this;} /** *

The access token for the request to update user attributes.

*/ inline UpdateUserAttributesRequest& WithAccessToken(Aws::String&& value) { SetAccessToken(std::move(value)); return *this;} /** *

The access token for the request to update user attributes.

*/ inline UpdateUserAttributesRequest& WithAccessToken(const char* value) { SetAccessToken(value); return *this;} /** *

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

    *
*/ inline const Aws::Map& GetClientMetadata() const{ return m_clientMetadata; } /** *

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

    *
*/ inline bool ClientMetadataHasBeenSet() const { return m_clientMetadataHasBeenSet; } /** *

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

    *
*/ inline void SetClientMetadata(const Aws::Map& value) { m_clientMetadataHasBeenSet = true; m_clientMetadata = value; } /** *

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

    *
*/ inline void SetClientMetadata(Aws::Map&& value) { m_clientMetadataHasBeenSet = true; m_clientMetadata = std::move(value); } /** *

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

    *
*/ inline UpdateUserAttributesRequest& WithClientMetadata(const Aws::Map& value) { SetClientMetadata(value); return *this;} /** *

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

    *
*/ inline UpdateUserAttributesRequest& WithClientMetadata(Aws::Map&& value) { SetClientMetadata(std::move(value)); return *this;} /** *

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

    *
*/ inline UpdateUserAttributesRequest& AddClientMetadata(const Aws::String& key, const Aws::String& value) { m_clientMetadataHasBeenSet = true; m_clientMetadata.emplace(key, value); return *this; } /** *

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

    *
*/ inline UpdateUserAttributesRequest& AddClientMetadata(Aws::String&& key, const Aws::String& value) { m_clientMetadataHasBeenSet = true; m_clientMetadata.emplace(std::move(key), value); return *this; } /** *

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

    *
*/ inline UpdateUserAttributesRequest& AddClientMetadata(const Aws::String& key, Aws::String&& value) { m_clientMetadataHasBeenSet = true; m_clientMetadata.emplace(key, std::move(value)); return *this; } /** *

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

    *
*/ inline UpdateUserAttributesRequest& AddClientMetadata(Aws::String&& key, Aws::String&& value) { m_clientMetadataHasBeenSet = true; m_clientMetadata.emplace(std::move(key), std::move(value)); return *this; } /** *

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

    *
*/ inline UpdateUserAttributesRequest& AddClientMetadata(const char* key, Aws::String&& value) { m_clientMetadataHasBeenSet = true; m_clientMetadata.emplace(key, std::move(value)); return *this; } /** *

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

    *
*/ inline UpdateUserAttributesRequest& AddClientMetadata(Aws::String&& key, const char* value) { m_clientMetadataHasBeenSet = true; m_clientMetadata.emplace(std::move(key), value); return *this; } /** *

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

    *
*/ inline UpdateUserAttributesRequest& AddClientMetadata(const char* key, const char* value) { m_clientMetadataHasBeenSet = true; m_clientMetadata.emplace(key, value); return *this; } private: Aws::Vector m_userAttributes; bool m_userAttributesHasBeenSet; Aws::String m_accessToken; bool m_accessTokenHasBeenSet; Aws::Map m_clientMetadata; bool m_clientMetadataHasBeenSet; }; } // namespace Model } // namespace CognitoIdentityProvider } // namespace Aws