Users don't understand how to change Git providers

[chrifro]

We get several support requests because users don't understand how to change git providers.

Common steps:

• they try to log in with another Git provider than they used the first time.
• they get the error "Email address already exists. Log in using a different provider."
• they are confused and contact support. Some are thinking the solution is deleting the account and creating a new one. So we could assume that some do that without contacting support.

https://gitpod.io/integrations doesn't seem to be obvious

possible solution:

• adjust error message
• allow login with another git provider as well (similar to how Vercel is doing it)

cc @gtsiolis

[AlexTugarev]

allow login with another git provider as well (similar to how Vercel is doing it)

@ChristinFrohne, do you have a story/description for that case?

[AlexTugarev]

@ChristinFrohne, I just checked with vercel.

The thing is, they are storing any Login Connections on backend indefinitely, i.e. even if you disconnect once and try to login, they remember your previous connection and let you in.

[JanKoehnlein]

Sounds like we can only do 1)

@gtsiolis can you provide us with a better error message?

/schedule

[roboquat]

@JanKoehnlein: Issue scheduled in the meta team (WIP: 0)

In response to this:

Sounds like we can only do 1)

@gtsiolis can you provide us with a better error message?

/schedule

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[JanKoehnlein]

/assign @jldec

[gtsiolis]

Following the comment in #6268 (comment), we could re-use one of the proposed alert titles:

1. Gitpod account already exists
2. Selected provider already in use

🍊 🍊 🍊 🍊

Wondering if this is a good time to split sign up and log in flows.

Use case 1️⃣: For example, instead of showing this error message we could ask:

Are you trying to login? It seems there's already an associated account with this email address. Log in

Use case 2️⃣: While if you explicitely visit the sign in page and you don't have an account associated with that email a user could be asked:

There's no existing account with this email address. Need to create an account? Create account

Use case 3️⃣: In the case where you try to select a different provider to create an account we could the user could be asked:

There's an existing Gitpod account using this email address. Try using a different provider and connecting more providers from integrations settings.

@AlexTugarev what do you think?

🍋 🍋 🍋 🍋

Also, @AlexTugarev regarding #5975 (comment), do you think this is something we don't want to aim for? Seems that Vercel bypasses all these issues we have using the approach of storing any login connections on backend indefinitely. ❓

[AlexTugarev]

I re-read the long story from above and good step forwards boils down to change the message from Email address already exists. Log in using a different provider. to Email address already in use in another account. Please login using github.com.

[AlexTugarev]

Also, @AlexTugarev regarding #5975 (comment), do you think this is something we don't want to aim for? Seems that Vercel bypasses all these issues we have using the approach of storing any login connections on backend indefinitely. ❓

@gtsiolis, while this definitely sounds like it can improve the UX, the downside is that we store account connection indefinitely. Do we want to do this?