-
Notifications
You must be signed in to change notification settings - Fork 9.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AWS Cognito: No option to stop mobile number update until verified #32408
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
You need to give more detail of what you're talking about as it's not clear at all but as far as I can see what you are asking for is already available at https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/cognito_user_pool#user_attribute_update_settings user_attribute_update_settings |
We want to signup users with email and we have kept SMS_MFA optional. So, to confirm the user we verify email. Now when the user wants to enable MFA. So, the user updates his phone number (updateUserAttributes) and then we send the verification code (getUserAttributeVerificationCode). But if the user does not verify his phone number then also the phone number gets updated in the Cognito. But this does not happen in the case of email, until the user does not verify his email, it does not changes as we have enabled - Keep original attribute value active when an update is pending - Recommended. In the given options, only email is enabled and the phone is disabled. |
This sounds like something you need to raise an AWS support ticket for rather than an AWS provider bug but you need to provide the Terraform code you are using. |
Description
I have select user verification through email. So, in sign up experience, want to keep Keep original attribute value active when an update is pending for Mobile number, but this option is disabled.
While signup user is entering his email and mobile number both, but we want user to confirm through email.
Affected Resource(s) and/or Data Source(s)
No response
Potential Terraform Configuration
No response
References
No response
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: