Detect if user is not confirmed prior authentication
See original GitHub issue** Which Category is your question related to? ** Auth
** What AWS Services are you utilizing? ** Cognito
** Provide additional details e.g. code snippets **
In our configuration Cognito user has to verify the email address or the phone number they used to register the account. If the user does not verify the account and tries to login, Amplify throws a UserNotFoundException
. Is there a way to distinguish wether the user is not registered from when they are registered but not confirmed?
Issue Analytics
- State:
- Created 4 years ago
- Comments:9 (2 by maintainers)
Top Results From Across the Web
How to check if user is confirmed in AWS Amplify?
I tried this check to see if it would return true or false , but no luck: console.log(await Auth.verifiedContact(this.state.email));.
Read more >Verify ID Tokens | Firebase Authentication - Google
First, find a third-party JWT library for your language. Then, verify the header, payload, and signature of the ID token. Must be in...
Read more >Check if your Gmail message is authenticated - Google Support
When an email isn't authenticated, that means Gmail doesn't know if the message is coming from the person who appears to be sending...
Read more >Email Verification - Using Autodesk Account
To protect your account and prevent fraud, you need to verify and confirm your ... If it's not in your spam folder, click...
Read more >Verify Emails using Auth0
A common way to verify emails with Auth0 is to email a magic link, or verification link, to the user. When the user...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Bump on this issue. It appears that if a user creates an account, but then leaves before being confirmed. And then later tries to:
So we do indeed need a way to know if the user is registered but not confirmed. In that case, when they try to sign in, they could sign in but then have to verify before proceeding.
I believe this ticket should be re-opened per the original description, which is slightly different than the last comment above. Steps to repro:
UserNotConfirmedException
UserNotFoundException
This leaves the client app no way to distinguish between a user trying to sign in who never created an account versus a user who signed up but never entered the code. Sure, the user can simply sign up again. But we’re having users call Support when they exit the app for whatever reason before completing registration. They expect to be prompted to enter the code when they go back in.