Look into Account creation sync/issues when using Google OAuth from other apps

[alex-ketch]

When a user signs up using OAuth from GSuita, a user account is created on the Hub, but not in Intercom.

I have not tried reproducing this issue yet, so cannot confirm that a bug actually exists. A user also tried to sign in to the Hub using the Google Auth button on the hub, but saw an error that their email was already taken. However, it would be nice to carry the user's sign-in status across apps. Not sure how feasible this is though.

[alex-ketch]

@nokome, I can confirm that this is still an issue on the latest deployments.

Steps to reproduce:

• Sign up from GSuita, and confirm authorization
• User is created on the hub, can create projects from sidebar, etc…
• Open hub.stenci.la and attempt to Sign In using Google OAuth button
• See a second authorization screen, but with less requested permissions this time
• Redirected to a screen stating: "You are about to use your Google account to login to hub.stenci.la. As a final step, please complete the following form:". Email field is repopulated with google email address.
• Enter username
• See an error stating: "An account already exists with this e-mail address. Please sign in to that account first, then connect your Google account."

Two observations:

• Seems there is some sort of discrepancy between the account authorizations requested, will need to look into seeing if it's possible to skip one of them.
• The account created from the sidebar doesn't seem to be a "fully formed" account, causing issues when trying to sign in

---

First authorization screen

Second authorization screen

[nokome]

I have made and deployed a fix which should allow for better matching based on email addresses (previously we we not creating an EmailAddress instance for Google users who authenticated with an OpenID token).

However, when a user authenticates with an add-on first, they will still need to authorise the Hub (although now when they do so that authorization should automatically get connected to the first Hub account they created). That is because the Hub and the Apps script add on are separates Outh clients with different ids and secrets:

One possible work around for this is for the add-on to send the Hub the Oauth access token and refresh token for each user when they authenticate with the addon?

I am unable to test this at the moment because the add-on is failing to load for me.