Table of Contents

Interface ICfnUserPoolUserProps

Namespace
Amazon.CDK.AWS.Cognito
Assembly
Amazon.CDK.AWS.Cognito.dll

Properties for defining a CfnUserPoolUser.

public interface ICfnUserPoolUserProps

Examples

// The code below shows an example of how to instantiate this type.
             // The values are placeholders you should change.
             using Amazon.CDK.AWS.Cognito;

             var clientMetadata;

             var cfnUserPoolUserProps = new CfnUserPoolUserProps {
                 UserPoolId = "userPoolId",

                 // the properties below are optional
                 ClientMetadata = clientMetadata,
                 DesiredDeliveryMediums = new [] { "desiredDeliveryMediums" },
                 ForceAliasCreation = false,
                 MessageAction = "messageAction",
                 UserAttributes = new [] { new AttributeTypeProperty {
                     Name = "name",
                     Value = "value"
                 } },
                 Username = "username",
                 ValidationData = new [] { new AttributeTypeProperty {
                     Name = "name",
                     Value = "value"
                 } }
             };

Remarks

Properties

ClientMetadata

A map of custom key-value pairs that you can provide as input for the custom workflow that is invoked by the pre sign-up trigger.

object? ClientMetadata { get; }

Property Value

object

Remarks

You create custom workflows by assigning AWS Lambda functions to user pool triggers. When you create a UserPoolUser resource and include the ClientMetadata property, Amazon Cognito invokes the function that is assigned to the pre sign-up 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 property. 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:

    Link: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-cognito-userpooluser.html#cfn-cognito-userpooluser-clientmetadata

    DesiredDeliveryMediums

    Specify "EMAIL" if email will be used to send the welcome message.

    string[]? DesiredDeliveryMediums { get; }

    Property Value

    string[]

    Remarks

    Specify "SMS" if the phone number will be used. The default value is "SMS" . You can specify more than one value.

    Link: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-cognito-userpooluser.html#cfn-cognito-userpooluser-desireddeliverymediums

    ForceAliasCreation

    This parameter is used only if the phone_number_verified or email_verified attribute is set to True .

    object? ForceAliasCreation { get; }

    Property Value

    object

    Remarks

    Otherwise, it is ignored.

    If this parameter is set to True and the phone number or email address specified in the UserAttributes parameter already exists as an alias with a different user, the API call will migrate the alias from the previous user to the newly created user. The previous user will no longer be able to log in using that alias.

    If this parameter is set to False , the API throws an AliasExistsException error if the alias already exists. The default value is False .

    Link: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-cognito-userpooluser.html#cfn-cognito-userpooluser-forcealiascreation

    MessageAction

    Set to RESEND to resend the invitation message to a user that already exists and reset the expiration limit on the user's account.

    string? MessageAction { get; }

    Property Value

    string

    Remarks

    UserAttributes

    The user attributes and attribute values to be set for the user to be created.

    object? UserAttributes { get; }

    Property Value

    object

    Remarks

    These are name-value pairs You can create a user without specifying any attributes other than Username . However, any attributes that you specify as required (in or in the Attributes tab of the console) must be supplied either by you (in your call to AdminCreateUser ) or by the user (when they sign up in response to your welcome message).

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

    To send a message inviting the user to sign up, you must specify the user's email address or phone number. This can be done in your call to AdminCreateUser or in the Users tab of the Amazon Cognito console for managing your user pools.

    In your call to AdminCreateUser , you can set the email_verified attribute to True , and you can set the phone_number_verified attribute to True . (You can also do this by calling .)

      Link: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-cognito-userpooluser.html#cfn-cognito-userpooluser-userattributes

      UserPoolId

      The user pool ID for the user pool where the user will be created.

      string UserPoolId { get; }

      Property Value

      string

      Remarks

      Username

      The username for the user.

      string? Username { get; }

      Property Value

      string

      Remarks

      Must be unique within the user pool. Must be a UTF-8 string between 1 and 128 characters. After the user is created, the username can't be changed.

      Link: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-cognito-userpooluser.html#cfn-cognito-userpooluser-username

      ValidationData

      The user's validation data.

      object? ValidationData { get; }

      Property Value

      object

      Remarks

      This is an array of name-value pairs that contain user attributes and attribute values that you can use for custom validation, such as restricting the types of user accounts that can be registered. For example, you might choose to allow or disallow user sign-up based on the user's domain.

      To configure custom validation, you must create a Pre Sign-up AWS Lambda trigger for the user pool as described in the Amazon Cognito Developer Guide. The Lambda trigger receives the validation data and uses it in the validation process.

      The user's validation data isn't persisted.

      Link: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-cognito-userpooluser.html#cfn-cognito-userpooluser-validationdata