Skip to content
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

Set account recovery preference #11220

Closed
pjlangley opened this issue Dec 10, 2019 · 12 comments · Fixed by #12444
Closed

Set account recovery preference #11220

pjlangley opened this issue Dec 10, 2019 · 12 comments · Fixed by #12444
Labels
enhancement Requests to existing resources that expand the functionality or scope.

Comments

@pjlangley
Copy link

Description

It'll be useful if we can set the user account recovery preference. The default without specification selects an option that's no longer recommended by AWS.

For example, I may want to set this to Email only instead, as annotated by the red rectangle in the image below:

account recover preference

As per my understanding, this doesn't yet appear to be supported by this resource.

New or Affected Resource(s)

  • aws_cognito_user_pool

References


Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment
@pjlangley pjlangley added the enhancement Requests to existing resources that expand the functionality or scope. label Dec 10, 2019
@ghost ghost added the service/cognito label Dec 10, 2019
@github-actions github-actions bot added the needs-triage Waiting for first response or review from a maintainer. label Dec 10, 2019
@hildoer
Copy link

hildoer commented Dec 20, 2019

+1

3 similar comments
@ghost
Copy link

ghost commented Jan 19, 2020

+1

@mtraynham
Copy link

+1

@tonesp
Copy link

tonesp commented Feb 12, 2020

+1

@davesalomon
Copy link

+1. On the plus side, there's been a recent change (for the better) to the defaults for Account Recovery. See https://docs.aws.amazon.com/cognito-user-identity-pools/latest/APIReference/API_CreateUserPool.html#CognitoUserPools-CreateUserPool-request-AccountRecoverySetting.

Starting February 1, 2020, the value of AccountRecoverySetting will default to verified_email first and verified_phone_number as the second option for newly created user pools if no value is provided.

@emulanob
Copy link

emulanob commented Jun 3, 2020

@davesalomon I created a few user pools today and they defaulted to the Not Recommended option.

@AlejandroGalAtSportBLX
Copy link

+1

@ewbankkit ewbankkit removed the needs-triage Waiting for first response or review from a maintainer. label Jul 29, 2020
@jeffrystev
Copy link

Did the above issue resolved ? Do we have any new parameters in terraform in order to update the recovery of account configuration in cognito . If so kindly update the newly added parameter over here.

@davesalomon
Copy link

Fairly sure this is still outstanding. AWS have also reverted their documentation back to 'Prefer SMS' 😞

In the absence of this setting, Cognito uses the legacy behavior to determine the recovery method where SMS is preferred over email.

@ScratZa
Copy link

ScratZa commented Oct 27, 2020

Has there been any communication with regards to this ?

Am I correct in assuming that the only work around is the local exec route ? I've seen quite a few people mentioning they would prefer not to use local exec - is there a reason for this ?

thanks a bunch

@breathingdust
Copy link
Member

Hi all! 👋 Just wanted to direct you to our public roadmap for this quarter (Nov-Jan) in which this item has been mentioned.

Due to the significant community interest in support for this feature, we will be looking at merging existing contributions soon.

We appreciate all the contributions and feedback thus far.

Look out for support in the provider soon!

@ghost
Copy link

ghost commented Dec 31, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!

@ghost ghost locked as resolved and limited conversation to collaborators Dec 31, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement Requests to existing resources that expand the functionality or scope.
Projects
None yet
Development

Successfully merging a pull request may close this issue.