Hi there! Are you looking for the official Deno documentation? Try docs.deno.com for all your Deno learning needs.

ResendConfirmationCodeRequest

import type { ResendConfirmationCodeRequest } from "https://aws-api.deno.dev/v0.4/services/cognitoidentityserviceprovider.ts?docs=full";

Represents the request to resend the confirmation code.

interface ResendConfirmationCodeRequest {
AnalyticsMetadata?: AnalyticsMetadataType | null;
ClientId: string;
ClientMetadata?: {
[key: string]: string | null | undefined;
}
| null;
SecretHash?: string | null;
UserContextData?: UserContextDataType | null;
Username: string;
}

§Properties

§
AnalyticsMetadata?: AnalyticsMetadataType | null
[src]

The Amazon Pinpoint analytics metadata that contributes to your metrics for ResendConfirmationCode calls.

§
ClientId: string
[src]

The ID of the client associated with the user pool.

§
ClientMetadata?: {
[key: string]: string | null | undefined;
}
| null
[src]

A map of custom key-value pairs that you can provide as input for any custom workflows that this action triggers.

You create custom workflows by assigning Lambda functions to user pool triggers. When you use the ResendConfirmationCode 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 ResendConfirmationCode request. In your function code in Lambda, you can process the clientMetadata value to enhance your workflow for your specific needs.

For more information, see Customizing user pool Workflows with Lambda Triggers in the Amazon Cognito Developer Guide.

Note: When you use the ClientMetadata parameter, remember that Amazon Cognito won't do the following: - Store the ClientMetadata value. This data is available only to Lambda triggers that are assigned to a user pool to support custom workflows. If your user pool configuration doesn't include triggers, the ClientMetadata parameter serves no purpose. - Validate the ClientMetadata value. - Encrypt the ClientMetadata value. Don't use Amazon Cognito to provide sensitive information.

§
SecretHash?: string | null
[src]

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.

§
UserContextData?: UserContextDataType | null
[src]

Contextual data about your user session, such as the device fingerprint, IP address, or location. Amazon Cognito advanced security evaluates the risk of an authentication event based on the context that your app generates and passes to Amazon Cognito when it makes API requests.

§
Username: string
[src]

The username attribute of the user to whom you want to resend a confirmation code.