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

Incorrect error message when password requirements not met #1054

Open
pb-jeff-oneill opened this issue Nov 30, 2023 · 3 comments
Open

Incorrect error message when password requirements not met #1054

pb-jeff-oneill opened this issue Nov 30, 2023 · 3 comments

Comments

@pb-jeff-oneill
Copy link

pb-jeff-oneill commented Nov 30, 2023

  • Operating System version: Mac OSX 13.6.2
  • Browser version: Chrome 119.0.6045.159
  • Firebase UI version: 6.1.0
  • Firebase SDK version: 10.4.0

I'm using Firebase Auth with Google Identity Platform and I recently set stricter password requirements than the defaults.

When a user goes through the password reset process and enters a password that doesn't meet the requirements, they see this message:

Try resetting your password again
Your request to reset your password has expired or the link has already been used

But this error message is incorrect.

The actual HTTP response is this:

{
  "error": {
    "code": 400,
    "message": "PASSWORD_DOES_NOT_MEET_REQUIREMENTS : Missing password requirements: [Password must contain at least 8 characters, Password must contain a lower case character, Password must contain an upper case character, Password must contain a non-alphanumeric character]",
    "errors": [
      {
        "message": "PASSWORD_DOES_NOT_MEET_REQUIREMENTS : Missing password requirements: [Password must contain at least 8 characters, Password must contain a lower case character, Password must contain an upper case character, Password must contain a non-alphanumeric character]",
        "domain": "global",
        "reason": "invalid"
      }
    ]
  }
}

It looks like firebaseui-web is ignoring the content of the HTTP response and using the "expired" message for all 400 errors.

Could you please update to provide the correct error message? This is very confusing for end users.

@jhuleatt
Copy link
Collaborator

jhuleatt commented Dec 4, 2023

Hi @pb-jeff-oneill, good news - this was fixed in #1047. We just need to run a release to get the error message fixes out. Expect a version 6.1.1 soon that has this fix.

@pb-jeff-oneill
Copy link
Author

Thank you. I'm looking forward to the 6.1.1 release!

@pb-jeff-oneill
Copy link
Author

Can you please deploy the 6.1.1 release? It has been months!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants