@Generated(value="com.amazonaws:aws-java-sdk-code-generator") public class AdminCreateUserRequest extends AmazonWebServiceRequest implements Serializable, Cloneable
Represents the request to create a user in the specified user pool.
NOOP
Constructor and Description |
---|
AdminCreateUserRequest() |
Modifier and Type | Method and Description |
---|---|
AdminCreateUserRequest |
addClientMetadataEntry(String key,
String value)
Add a single ClientMetadata entry
|
AdminCreateUserRequest |
clearClientMetadataEntries()
Removes all the entries added into ClientMetadata.
|
AdminCreateUserRequest |
clone()
Creates a shallow clone of this object for all fields except the handler context.
|
boolean |
equals(Object obj) |
Map<String,String> |
getClientMetadata()
A map of custom key-value pairs that you can provide as input for any custom workflows that this action triggers.
|
List<String> |
getDesiredDeliveryMediums()
Specify
"EMAIL" if email will be used to send the welcome message. |
Boolean |
getForceAliasCreation()
This parameter is used only if the
phone_number_verified or email_verified attribute is
set to True . |
String |
getMessageAction()
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 |
getTemporaryPassword()
The user's temporary password.
|
List<AttributeType> |
getUserAttributes()
An array of name-value pairs that contain user attributes and attribute values to be set for the user to be
created.
|
String |
getUsername()
The username for the user.
|
String |
getUserPoolId()
The user pool ID for the user pool where the user will be created.
|
List<AttributeType> |
getValidationData()
The user's validation data.
|
int |
hashCode() |
Boolean |
isForceAliasCreation()
This parameter is used only if the
phone_number_verified or email_verified attribute is
set to True . |
void |
setClientMetadata(Map<String,String> clientMetadata)
A map of custom key-value pairs that you can provide as input for any custom workflows that this action triggers.
|
void |
setDesiredDeliveryMediums(Collection<String> desiredDeliveryMediums)
Specify
"EMAIL" if email will be used to send the welcome message. |
void |
setForceAliasCreation(Boolean forceAliasCreation)
This parameter is used only if the
phone_number_verified or email_verified attribute is
set to True . |
void |
setMessageAction(MessageActionType 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. |
void |
setMessageAction(String 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. |
void |
setTemporaryPassword(String temporaryPassword)
The user's temporary password.
|
void |
setUserAttributes(Collection<AttributeType> userAttributes)
An array of name-value pairs that contain user attributes and attribute values to be set for the user to be
created.
|
void |
setUsername(String username)
The username for the user.
|
void |
setUserPoolId(String userPoolId)
The user pool ID for the user pool where the user will be created.
|
void |
setValidationData(Collection<AttributeType> validationData)
The user's validation data.
|
String |
toString()
Returns a string representation of this object.
|
AdminCreateUserRequest |
withClientMetadata(Map<String,String> clientMetadata)
A map of custom key-value pairs that you can provide as input for any custom workflows that this action triggers.
|
AdminCreateUserRequest |
withDesiredDeliveryMediums(Collection<String> desiredDeliveryMediums)
Specify
"EMAIL" if email will be used to send the welcome message. |
AdminCreateUserRequest |
withDesiredDeliveryMediums(DeliveryMediumType... desiredDeliveryMediums)
Specify
"EMAIL" if email will be used to send the welcome message. |
AdminCreateUserRequest |
withDesiredDeliveryMediums(String... desiredDeliveryMediums)
Specify
"EMAIL" if email will be used to send the welcome message. |
AdminCreateUserRequest |
withForceAliasCreation(Boolean forceAliasCreation)
This parameter is used only if the
phone_number_verified or email_verified attribute is
set to True . |
AdminCreateUserRequest |
withMessageAction(MessageActionType 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. |
AdminCreateUserRequest |
withMessageAction(String 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. |
AdminCreateUserRequest |
withTemporaryPassword(String temporaryPassword)
The user's temporary password.
|
AdminCreateUserRequest |
withUserAttributes(AttributeType... userAttributes)
An array of name-value pairs that contain user attributes and attribute values to be set for the user to be
created.
|
AdminCreateUserRequest |
withUserAttributes(Collection<AttributeType> userAttributes)
An array of name-value pairs that contain user attributes and attribute values to be set for the user to be
created.
|
AdminCreateUserRequest |
withUsername(String username)
The username for the user.
|
AdminCreateUserRequest |
withUserPoolId(String userPoolId)
The user pool ID for the user pool where the user will be created.
|
AdminCreateUserRequest |
withValidationData(AttributeType... validationData)
The user's validation data.
|
AdminCreateUserRequest |
withValidationData(Collection<AttributeType> validationData)
The user's validation data.
|
addHandlerContext, getCloneRoot, getCloneSource, getCustomQueryParameters, getCustomRequestHeaders, getGeneralProgressListener, getHandlerContext, getReadLimit, getRequestClientOptions, getRequestCredentials, getRequestCredentialsProvider, getRequestMetricCollector, getSdkClientExecutionTimeout, getSdkRequestTimeout, putCustomQueryParameter, putCustomRequestHeader, setGeneralProgressListener, setRequestCredentials, setRequestCredentialsProvider, setRequestMetricCollector, setSdkClientExecutionTimeout, setSdkRequestTimeout, withGeneralProgressListener, withRequestCredentialsProvider, withRequestMetricCollector, withSdkClientExecutionTimeout, withSdkRequestTimeout
public void setUserPoolId(String userPoolId)
The user pool ID for the user pool where the user will be created.
userPoolId
- The user pool ID for the user pool where the user will be created.public String getUserPoolId()
The user pool ID for the user pool where the user will be created.
public AdminCreateUserRequest withUserPoolId(String userPoolId)
The user pool ID for the user pool where the user will be created.
userPoolId
- The user pool ID for the user pool where the user will be created.public void setUsername(String username)
The username for the user. 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.
username
- The username for the user. 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.public String getUsername()
The username for the user. 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.
public AdminCreateUserRequest withUsername(String username)
The username for the user. 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.
username
- The username for the user. 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.public List<AttributeType> getUserAttributes()
An array of name-value pairs that contain user attributes and attribute values to be set for the user to be
created. You can create a user without specifying any attributes other than Username
. However, any
attributes that you specify as required (when creating a user pool or in the Attributes tab of the
console) either you should supply (in your call to AdminCreateUser
) or the user should supply (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. You can do this 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 AdminUpdateUserAttributes.
email: The email address of the user to whom the message that contains the code and username will be sent.
Required if the email_verified
attribute is set to True
, or if "EMAIL"
is
specified in the DesiredDeliveryMediums
parameter.
phone_number: The phone number of the user to whom the message that contains the code and username will be
sent. Required if the phone_number_verified
attribute is set to True
, or if
"SMS"
is specified in the DesiredDeliveryMediums
parameter.
Username
.
However, any attributes that you specify as required (when creating a user pool or in the
Attributes tab of the console) either you should supply (in your call to
AdminCreateUser
) or the user should supply (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. You can do this 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 AdminUpdateUserAttributes.
email: The email address of the user to whom the message that contains the code and username will
be sent. Required if the email_verified
attribute is set to True
, or if
"EMAIL"
is specified in the DesiredDeliveryMediums
parameter.
phone_number: The phone number of the user to whom the message that contains the code and username
will be sent. Required if the phone_number_verified
attribute is set to True
,
or if "SMS"
is specified in the DesiredDeliveryMediums
parameter.
public void setUserAttributes(Collection<AttributeType> userAttributes)
An array of name-value pairs that contain user attributes and attribute values to be set for the user to be
created. You can create a user without specifying any attributes other than Username
. However, any
attributes that you specify as required (when creating a user pool or in the Attributes tab of the
console) either you should supply (in your call to AdminCreateUser
) or the user should supply (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. You can do this 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 AdminUpdateUserAttributes.
email: The email address of the user to whom the message that contains the code and username will be sent.
Required if the email_verified
attribute is set to True
, or if "EMAIL"
is
specified in the DesiredDeliveryMediums
parameter.
phone_number: The phone number of the user to whom the message that contains the code and username will be
sent. Required if the phone_number_verified
attribute is set to True
, or if
"SMS"
is specified in the DesiredDeliveryMediums
parameter.
userAttributes
- An array of name-value pairs that contain user attributes and attribute values to be set for the user to
be created. You can create a user without specifying any attributes other than Username
.
However, any attributes that you specify as required (when creating a user pool or in the
Attributes tab of the console) either you should supply (in your call to
AdminCreateUser
) or the user should supply (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. You can do this 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 AdminUpdateUserAttributes.
email: The email address of the user to whom the message that contains the code and username will
be sent. Required if the email_verified
attribute is set to True
, or if
"EMAIL"
is specified in the DesiredDeliveryMediums
parameter.
phone_number: The phone number of the user to whom the message that contains the code and username
will be sent. Required if the phone_number_verified
attribute is set to True
, or
if "SMS"
is specified in the DesiredDeliveryMediums
parameter.
public AdminCreateUserRequest withUserAttributes(AttributeType... userAttributes)
An array of name-value pairs that contain user attributes and attribute values to be set for the user to be
created. You can create a user without specifying any attributes other than Username
. However, any
attributes that you specify as required (when creating a user pool or in the Attributes tab of the
console) either you should supply (in your call to AdminCreateUser
) or the user should supply (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. You can do this 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 AdminUpdateUserAttributes.
email: The email address of the user to whom the message that contains the code and username will be sent.
Required if the email_verified
attribute is set to True
, or if "EMAIL"
is
specified in the DesiredDeliveryMediums
parameter.
phone_number: The phone number of the user to whom the message that contains the code and username will be
sent. Required if the phone_number_verified
attribute is set to True
, or if
"SMS"
is specified in the DesiredDeliveryMediums
parameter.
NOTE: This method appends the values to the existing list (if any). Use
setUserAttributes(java.util.Collection)
or withUserAttributes(java.util.Collection)
if you want
to override the existing values.
userAttributes
- An array of name-value pairs that contain user attributes and attribute values to be set for the user to
be created. You can create a user without specifying any attributes other than Username
.
However, any attributes that you specify as required (when creating a user pool or in the
Attributes tab of the console) either you should supply (in your call to
AdminCreateUser
) or the user should supply (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. You can do this 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 AdminUpdateUserAttributes.
email: The email address of the user to whom the message that contains the code and username will
be sent. Required if the email_verified
attribute is set to True
, or if
"EMAIL"
is specified in the DesiredDeliveryMediums
parameter.
phone_number: The phone number of the user to whom the message that contains the code and username
will be sent. Required if the phone_number_verified
attribute is set to True
, or
if "SMS"
is specified in the DesiredDeliveryMediums
parameter.
public AdminCreateUserRequest withUserAttributes(Collection<AttributeType> userAttributes)
An array of name-value pairs that contain user attributes and attribute values to be set for the user to be
created. You can create a user without specifying any attributes other than Username
. However, any
attributes that you specify as required (when creating a user pool or in the Attributes tab of the
console) either you should supply (in your call to AdminCreateUser
) or the user should supply (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. You can do this 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 AdminUpdateUserAttributes.
email: The email address of the user to whom the message that contains the code and username will be sent.
Required if the email_verified
attribute is set to True
, or if "EMAIL"
is
specified in the DesiredDeliveryMediums
parameter.
phone_number: The phone number of the user to whom the message that contains the code and username will be
sent. Required if the phone_number_verified
attribute is set to True
, or if
"SMS"
is specified in the DesiredDeliveryMediums
parameter.
userAttributes
- An array of name-value pairs that contain user attributes and attribute values to be set for the user to
be created. You can create a user without specifying any attributes other than Username
.
However, any attributes that you specify as required (when creating a user pool or in the
Attributes tab of the console) either you should supply (in your call to
AdminCreateUser
) or the user should supply (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. You can do this 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 AdminUpdateUserAttributes.
email: The email address of the user to whom the message that contains the code and username will
be sent. Required if the email_verified
attribute is set to True
, or if
"EMAIL"
is specified in the DesiredDeliveryMediums
parameter.
phone_number: The phone number of the user to whom the message that contains the code and username
will be sent. Required if the phone_number_verified
attribute is set to True
, or
if "SMS"
is specified in the DesiredDeliveryMediums
parameter.
public List<AttributeType> getValidationData()
The user's validation data. 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 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.
To configure custom validation, you must create a Pre Sign-up 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.
public void setValidationData(Collection<AttributeType> validationData)
The user's validation data. 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 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.
validationData
- The user's validation data. 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 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.
public AdminCreateUserRequest withValidationData(AttributeType... validationData)
The user's validation data. 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 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.
NOTE: This method appends the values to the existing list (if any). Use
setValidationData(java.util.Collection)
or withValidationData(java.util.Collection)
if you want
to override the existing values.
validationData
- The user's validation data. 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 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.
public AdminCreateUserRequest withValidationData(Collection<AttributeType> validationData)
The user's validation data. 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 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.
validationData
- The user's validation data. 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 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.
public void setTemporaryPassword(String temporaryPassword)
The user's temporary password. This password must conform to the password policy that you specified when you created the user pool.
The temporary password is valid only once. To complete the Admin Create User flow, the user must enter the temporary password in the sign-in page, along with a new password to be used in all future sign-ins.
This parameter isn't required. If you don't specify a value, Amazon Cognito generates one for you.
The temporary password can only be used until the user account expiration limit that you specified when you
created the user pool. To reset the account after that time limit, you must call AdminCreateUser
again, specifying "RESEND"
for the MessageAction
parameter.
temporaryPassword
- The user's temporary password. This password must conform to the password policy that you specified when
you created the user pool.
The temporary password is valid only once. To complete the Admin Create User flow, the user must enter the temporary password in the sign-in page, along with a new password to be used in all future sign-ins.
This parameter isn't required. If you don't specify a value, Amazon Cognito generates one for you.
The temporary password can only be used until the user account expiration limit that you specified when
you created the user pool. To reset the account after that time limit, you must call
AdminCreateUser
again, specifying "RESEND"
for the MessageAction
parameter.
public String getTemporaryPassword()
The user's temporary password. This password must conform to the password policy that you specified when you created the user pool.
The temporary password is valid only once. To complete the Admin Create User flow, the user must enter the temporary password in the sign-in page, along with a new password to be used in all future sign-ins.
This parameter isn't required. If you don't specify a value, Amazon Cognito generates one for you.
The temporary password can only be used until the user account expiration limit that you specified when you
created the user pool. To reset the account after that time limit, you must call AdminCreateUser
again, specifying "RESEND"
for the MessageAction
parameter.
The temporary password is valid only once. To complete the Admin Create User flow, the user must enter the temporary password in the sign-in page, along with a new password to be used in all future sign-ins.
This parameter isn't required. If you don't specify a value, Amazon Cognito generates one for you.
The temporary password can only be used until the user account expiration limit that you specified when
you created the user pool. To reset the account after that time limit, you must call
AdminCreateUser
again, specifying "RESEND"
for the MessageAction
parameter.
public AdminCreateUserRequest withTemporaryPassword(String temporaryPassword)
The user's temporary password. This password must conform to the password policy that you specified when you created the user pool.
The temporary password is valid only once. To complete the Admin Create User flow, the user must enter the temporary password in the sign-in page, along with a new password to be used in all future sign-ins.
This parameter isn't required. If you don't specify a value, Amazon Cognito generates one for you.
The temporary password can only be used until the user account expiration limit that you specified when you
created the user pool. To reset the account after that time limit, you must call AdminCreateUser
again, specifying "RESEND"
for the MessageAction
parameter.
temporaryPassword
- The user's temporary password. This password must conform to the password policy that you specified when
you created the user pool.
The temporary password is valid only once. To complete the Admin Create User flow, the user must enter the temporary password in the sign-in page, along with a new password to be used in all future sign-ins.
This parameter isn't required. If you don't specify a value, Amazon Cognito generates one for you.
The temporary password can only be used until the user account expiration limit that you specified when
you created the user pool. To reset the account after that time limit, you must call
AdminCreateUser
again, specifying "RESEND"
for the MessageAction
parameter.
public void setForceAliasCreation(Boolean forceAliasCreation)
This parameter is used only if the phone_number_verified
or email_verified
attribute is
set to True
. 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
.
forceAliasCreation
- This parameter is used only if the phone_number_verified
or email_verified
attribute is set to True
. 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
.
public Boolean getForceAliasCreation()
This parameter is used only if the phone_number_verified
or email_verified
attribute is
set to True
. 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
.
phone_number_verified
or email_verified
attribute is set to True
. 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
.
public AdminCreateUserRequest withForceAliasCreation(Boolean forceAliasCreation)
This parameter is used only if the phone_number_verified
or email_verified
attribute is
set to True
. 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
.
forceAliasCreation
- This parameter is used only if the phone_number_verified
or email_verified
attribute is set to True
. 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
.
public Boolean isForceAliasCreation()
This parameter is used only if the phone_number_verified
or email_verified
attribute is
set to True
. 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
.
phone_number_verified
or email_verified
attribute is set to True
. 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
.
public void setMessageAction(String 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. Set to SUPPRESS
to suppress sending the message. You can
specify only one value.
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. Set to SUPPRESS
to suppress sending the message. You
can specify only one value.MessageActionType
public String getMessageAction()
Set to RESEND
to resend the invitation message to a user that already exists and reset the
expiration limit on the user's account. Set to SUPPRESS
to suppress sending the message. You can
specify only one value.
RESEND
to resend the invitation message to a user that already exists and reset the
expiration limit on the user's account. Set to SUPPRESS
to suppress sending the message. You
can specify only one value.MessageActionType
public AdminCreateUserRequest withMessageAction(String 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. Set to SUPPRESS
to suppress sending the message. You can
specify only one value.
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. Set to SUPPRESS
to suppress sending the message. You
can specify only one value.MessageActionType
public void setMessageAction(MessageActionType 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. Set to SUPPRESS
to suppress sending the message. You can
specify only one value.
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. Set to SUPPRESS
to suppress sending the message. You
can specify only one value.MessageActionType
public AdminCreateUserRequest withMessageAction(MessageActionType 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. Set to SUPPRESS
to suppress sending the message. You can
specify only one value.
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. Set to SUPPRESS
to suppress sending the message. You
can specify only one value.MessageActionType
public List<String> getDesiredDeliveryMediums()
Specify "EMAIL"
if email will be used to send the welcome message. Specify "SMS"
if the
phone number will be used. The default value is "SMS"
. You can specify more than one value.
"EMAIL"
if email will be used to send the welcome message. Specify
"SMS"
if the phone number will be used. The default value is "SMS"
. You can
specify more than one value.DeliveryMediumType
public void setDesiredDeliveryMediums(Collection<String> desiredDeliveryMediums)
Specify "EMAIL"
if email will be used to send the welcome message. Specify "SMS"
if the
phone number will be used. The default value is "SMS"
. You can specify more than one value.
desiredDeliveryMediums
- Specify "EMAIL"
if email will be used to send the welcome message. Specify "SMS"
if the phone number will be used. The default value is "SMS"
. You can specify more than one
value.DeliveryMediumType
public AdminCreateUserRequest withDesiredDeliveryMediums(String... desiredDeliveryMediums)
Specify "EMAIL"
if email will be used to send the welcome message. Specify "SMS"
if the
phone number will be used. The default value is "SMS"
. You can specify more than one value.
NOTE: This method appends the values to the existing list (if any). Use
setDesiredDeliveryMediums(java.util.Collection)
or
withDesiredDeliveryMediums(java.util.Collection)
if you want to override the existing values.
desiredDeliveryMediums
- Specify "EMAIL"
if email will be used to send the welcome message. Specify "SMS"
if the phone number will be used. The default value is "SMS"
. You can specify more than one
value.DeliveryMediumType
public AdminCreateUserRequest withDesiredDeliveryMediums(Collection<String> desiredDeliveryMediums)
Specify "EMAIL"
if email will be used to send the welcome message. Specify "SMS"
if the
phone number will be used. The default value is "SMS"
. You can specify more than one value.
desiredDeliveryMediums
- Specify "EMAIL"
if email will be used to send the welcome message. Specify "SMS"
if the phone number will be used. The default value is "SMS"
. You can specify more than one
value.DeliveryMediumType
public AdminCreateUserRequest withDesiredDeliveryMediums(DeliveryMediumType... desiredDeliveryMediums)
Specify "EMAIL"
if email will be used to send the welcome message. Specify "SMS"
if the
phone number will be used. The default value is "SMS"
. You can specify more than one value.
desiredDeliveryMediums
- Specify "EMAIL"
if email will be used to send the welcome message. Specify "SMS"
if the phone number will be used. The default value is "SMS"
. You can specify more than one
value.DeliveryMediumType
public Map<String,String> getClientMetadata()
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 AdminCreateUser
API action, 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
parameter in your AdminCreateUser 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.
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.
You create custom workflows by assigning Lambda functions to user pool triggers. When you use the
AdminCreateUser API action, 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 parameter in your AdminCreateUser 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.
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.
public void setClientMetadata(Map<String,String> 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 Lambda functions to user pool triggers. When you use the AdminCreateUser
API action, 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
parameter in your AdminCreateUser 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.
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.
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 Lambda functions to user pool triggers. When you use the
AdminCreateUser API action, 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 parameter in your AdminCreateUser 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.
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.
public AdminCreateUserRequest withClientMetadata(Map<String,String> 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 Lambda functions to user pool triggers. When you use the AdminCreateUser
API action, 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
parameter in your AdminCreateUser 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.
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.
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 Lambda functions to user pool triggers. When you use the
AdminCreateUser API action, 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 parameter in your AdminCreateUser 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.
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.
public AdminCreateUserRequest addClientMetadataEntry(String key, String value)
public AdminCreateUserRequest clearClientMetadataEntries()
public String toString()
toString
in class Object
Object.toString()
public AdminCreateUserRequest clone()
AmazonWebServiceRequest
clone
in class AmazonWebServiceRequest
Object.clone()