Closed careignition-cps closed 2 years ago
I had this same issue. Cognito recently rolled out a new console and suddenly my test account usernames and passwords didn't work. To fix, try:
app integration
tab.app client list
. Click on your app.app client information
. Click edit
.prevent user existence errors
.When I unchecked this my u/p worked again, then I checked it back and they still work as expected. Hope this helps!
Hi @careignition-cps 👋 thanks for raising this issue. Can you try @jamessouth's steps and see if that helps at all? If not, I'll try to reproduce the issue and see if I can find a solution/workaround for you.
Hi 👋 Closing this as we have not heard back from you. If you are still experiencing this issue and in need of assistance, please feel free to comment and provide us with any information previously requested by our team members so we can re-open this issue and be better able to assist you. Thank you!
If you are here because you have a similar error and you cannot find the answer, when you create a user from the admin or with the admin sdk from the frontend you have to use the authentication flow "USER_PASSWORD_AUTH" previously you should have configured it in the app client:
https://docs.amplify.aws/lib/auth/switch-auth/q/platform/js/
Thank you @visomi-dev this just saved me! In order for the app client to perform ChangePassword you have to allow the app client to perform the flow "USER_PASSWORD_AUTH".
Before opening, please confirm:
JavaScript Framework
React
Amplify APIs
Authentication
Amplify Categories
auth
Environment information
Describe the bug
I have been able to log in and log out for a while with the exact same email and password combination. However, now, every time I try to log in (I tried the following cases: disabled my user on the console, reset my users passcode on the console) I get the error: NotAuthorizedException: Incorrect username or password.
To check if I am just not remembering right, I created a NEW user. The user now has the status FORCE_CHANGE_PASSWORD on the console. However, my console is logging the same error, not authorized.
Expected behavior
Expected behavior: being able to log in with correct credentials and being able to get any error other than NotAuthorizedException.
Reproduction steps
I yarn start my project and
This worked two weeks ago, I have changed no code. I simply signed out for the first time in three weeks
Code Snippet
User pool
GetLoggedInStatus
Log output
See screenshot above
aws-exports.js
No response
Manual configuration
No response
Additional configuration
No response
Mobile Device
No response
Mobile Operating System
No response
Mobile Browser
No response
Mobile Browser Version
No response
Additional information and screenshots
No response