Sign in with Google or GitHub

Alongside a password, a magic link and single sign-on, SupaCloud can sign you in with a social provider — currently Google and GitHub.

Note

Social login is off by default. You will only see the buttons if your instance’s operator has configured that provider. If the sign-in page shows no social buttons, ask your administrator to enable one — see Enable social login and the captcha.

Sign in with a provider

1. Open the sign-in page. Under the email field you will find a button for each provider your instance has enabled.

2. Choose Continue with Google or Continue with GitHub. You are sent to the provider, where you approve the sign-in.

3. You land back in SupaCloud, signed in.

If your email address is not yet known to SupaCloud, a new account is created for you — exactly as if you had signed up normally. Any workspace invitations waiting for that address are claimed at that moment.

If you already have an account

If the address the provider gives us already belongs to an account that has not yet linked this provider, we will not sign you in and we will not merge the two. You will see “an account already exists”. Sign in with the method you already use, then link the provider from your settings (below).

This is deliberate. Automatically trusting an email address from a provider is how accounts get taken over. We only ever link a provider to your account when you, already signed in, ask us to.

Two-factor authentication still applies

If you have an authenticator app switched on, signing in with a provider still asks for your six-digit code. Your second factor belongs to your SupaCloud account, not to Google or GitHub.

Tip

This is different from enterprise single sign-on (SSO), where your identity provider owns the second factor.

Link or unlink a provider

1. Go to Settings → Connected accounts.

2. Press Connect next to a provider. You approve the sign-in once, and the provider is bound to your account.

3. To remove one, press Disconnect.

Caution

You cannot disconnect your last remaining way to sign in. If a social provider is the only method on your account, set a password (or link a second provider) before disconnecting it — otherwise you would lock yourself out.

A provider identity can only ever belong to one SupaCloud account, and your account can hold at most one identity per provider.

The captcha you may occasionally see

When your operator has enabled it, a small verification step appears while you register, request a magic link, reset your password, or ask for a new verification email — and when signing in after several failed attempts.

Your browser solves it silently; there is nothing to click and no images to identify. It is computed entirely on your instance — no third-party script runs and no data about you leaves the server.

Note

The check needs a secure (HTTPS) connection. On a plain http:// origin your browser does not expose the cryptography it needs, and SupaCloud will tell you so rather than leaving you with a button that can never succeed.

Related

• Enable social login and the captcha — for administrators
• Configure OIDC SSO — enterprise single sign-on