Hello, About supabase auth. I'm reporting an incident when updating to a new email. please see the scenario below. - Me as a user. Created a new account with Google provider (me@gmail.com) - success! - Later... I've decided to change my email to a regular email (me@anyemail.com) - success! - No problem, It's working. I can login with my new regular email (me@anyemail.com) - However, when I tried to login through Google with my previous email (me@gmail.com) it's still working! I still can be authenticated with it on behalf of the new regular email. In reality, this previous Gmail shouldn't be able to login. - Any suggestions on how to solve this? The documentation says only for a regular update email scenario.

Hello @Keeko! This thread has been automatically created from your message in #843999948717555735 a ``few seconds ago``. Pinging @User so that they see this as well! Want to unsubscribe from this thread? Right-click the thread in Discord (or use the ... menu) and select Leave Thread to unsubscribe from future updates. Want to change the title? Use the

/title

command! We have solved your problem? Click the button below to archive it.

Interesting. You probably want to post that as an issue in github supabase/gotrue I did not see that particular bug (if true) mentioned. It would help if you showed your auth.user email and raw_app_meta_data. It would even be better to include any rows for that uid in auth.identities table. I thought things keyed on email as identifier, but evidently no.

Keeko (2022-04-30)

Yep will do, thanks. I'll do a bit more investigating before that 🙂