Closed andyfurniss4 closed 4 years ago
I'll try to repro this. It may be that the user is confirmed but not the email. These are two different things for Cognito
Yeah, I understand they are different things but I would have thought if verification is disabled then it shouldn't matter that the email is not verified? Also, it allowed me to log in before changing the email and at no point has email_verified been 'true'.
Hi @andyfurniss4,
Good afternoon.
I was going through the issue backlog and came across this issue. I'm not sure if this helps, but there was a similar issue reported in https://github.com/aws-amplify/amplify-js repository where user changes the email address. Someone from Cognito team provided a workaround or reasons this is an issue, please refer https://github.com/aws-amplify/amplify-js/issues/987#issuecomment-531025897. Please see if the other issue provides some help.
Thanks, Ashish
This issue has not recieved a response in 2 weeks. If you want to keep this issue open, please just leave a comment below and auto-close will be canceled.
The user registration flow for my application is as follows:
UserManager.CreateAsync()
)UserManager.SetEmailAsync()
).I have disabled verification in Cognito for my user pool:
I have done this because I don't want the emails to be sent immediately after the user registers, I do actually want them to verify their email but not until the admin approval has taken place. I can't see a way to manually send the email with the .NET Identity API (can you confirm?) so I intend to build my own email system for this at a later time.
The problem I'm having is if the user decides to change their email, and then logs out and tries to log back in with their new email, I get a
UserNotConfirmedException
. I've checked the status of the user in Cognito and it's still CONFIRMED so I'm not really sure what the correct process is here.I've also tried adding an extra call to
AdminConfirmSignUpAsync()
after the user changes their email but I just get an exception saying the user is already CONFIRMED which I guess is expected. However, the user is now in a state where it IS confirmed but can't log in and verification is disabled.I understand this may not be within the scope of this project and may be an underlying issue but I figured I'd get your input first!