You are viewing documentation for version 2 of the AWS SDK for Ruby. Version 3 documentation can be found here.
Class: Aws::CognitoIdentityProvider::Types::GetUserAttributeVerificationCodeRequest
- Inherits:
-
Struct
- Object
- Struct
- Aws::CognitoIdentityProvider::Types::GetUserAttributeVerificationCodeRequest
- Defined in:
- (unknown)
Overview
When passing GetUserAttributeVerificationCodeRequest as input to an Aws::Client method, you can use a vanilla Hash:
{
access_token: "TokenModelType", # required
attribute_name: "AttributeNameType", # required
client_metadata: {
"StringType" => "StringType",
},
}
Represents the request to get user attribute verification.
Instance Attribute Summary collapse
-
#access_token ⇒ String
The access token returned by the server response to get the user attribute verification code.
-
#attribute_name ⇒ String
The attribute name returned by the server response to get the user attribute verification code.
-
#client_metadata ⇒ Hash<String,String>
A map of custom key-value pairs that you can provide as input for any custom workflows that this action triggers.
Instance Attribute Details
#access_token ⇒ String
The access token returned by the server response to get the user attribute verification code.
#attribute_name ⇒ String
The attribute name returned by the server response to get the user attribute verification code.
#client_metadata ⇒ Hash<String,String>
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 GetUserAttributeVerificationCode 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
GetUserAttributeVerificationCode 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.
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.