No way to add providers to an existing user

[globemediaofficial]

With Firebase, I was able to do the following:

final credential = GoogleAuthProvider.credential(idToken: idToken);
//OR OTHER PROVIDERS
final credential = EmailAuthProvider.credential(email: emailAddress, password: password);
//ADD PROVIDER TO CURRENT USER
FirebaseAuth.instance.currentUser?.linkWithCredential(credential);

With Supabase I know these two things; users can be created with OAuth providers and, if the email of that provider user matches an existing user email, the provider is automatically added to that existing user. What I don't know is how to add providers to a user manually. This is a pretty standard feature with authentication on apps. I saw one answer on StackOverflow that suggests it isn't possible on Supabase, because "currently in Supabase email address is the unique identifier of users," but I don't think this is the case. I think this would be a great addition to Supabase Auth (self-hosted).

Example 1:

1. App requires every user to have an Email & Password
2. User signs up with phone auth or OAth
3. User needs to add Email & Password provider to their profile

Example 2:

1. User signs up with an Email & Password provider
2. User wants to be able to sign in with OAuth or phone auth
3. User needs to sign in to OAuth then that provider should be added to the existing Email & Password account, regardless of if the email matches

[tkrunning]

I've also run into this issue.

It seems it's currently supported that OAuth and email address don't match (e.g. if you change the account email after the OAuth provider is connected, you can still log in with the provider), but it's not a good workaround to ask users to temporarily change their account email address to the one matching their OAuth provider before adding it.

[hf]

This is one of the highest priorities for the team in the coming period. Watch this space. Somewhat related to #68.

[hf]

Actually, a duplicate of #313.

[globemediaofficial]

@hf Since this issue was closed as "not planned," is this no longer a priority for the team? I'm confused because you said this issue was one of the highest priorities for the team and then closed it as not planned on the same day.