User can't sign in with Google after email address change

[Pfaufisch]

What happened?

After changing a user's email address in our Google Workspace, they can no longer sign in to LibreChat using their Google account. LibreChat shows an error message:

{"messages":"An document with that [\"googleId\"] already exists.","fields":"[\"googleId\"]"}

Maybe LibreChat doesn't recognize the email address and attempts to create a new user, which then fails when it attempts to reuse the (Google) account ID?

Version Information

v0.8.0

Steps to Reproduce

1. Have an existing account in LibreChat using the Google login
2. Change the primary email address of that account
3. Sign-in to LibreChat using Google

What browsers are you seeing the problem on?

No response

Relevant log output

{"messages":"An document with that [\"googleId\"] already exists.","fields":"[\"googleId\"]"}

Screenshots

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[danny-avila]

See the discussion here: #9713

[danny-avila]

Also, the googleId is likely the same even though the email address is different. You will have to edit the database user document to update the email.

[res-tractive]

@danny-avila correct me but can't be the google login be considered as safe and regardless which email the google account has it should be then also reflected in LibreChat? Or don't compare at least the email addresses for social logins?

We have currently the same issue after a marriage and the last name changed. So I would guess this could happen more often.

We will try you solution with updating the database directly but would be great if another solution is considered for this.

And thanks for the great work with LibreChat.

[Pfaufisch]

Thanks for the guidance! The manual database update worked and resolved the issue.

However, as res-tractive pointed out, this shouldn't actually be necessary if LibreChat uses the Google account ID for authentication. Since the googleId remains the same regardless of email changes, LibreChat should ideally handle this automatically.

It's worth noting that this is different from discussion #9713 – in that case, users switched authentication providers entirely. In our situation, no provider change occurred; it's the same Google account with the same ID, just with an updated email address.

[danny-avila]

Thanks, noted and I will look into it.

[danny-avila]

opened issue: #10348