Social sign-in

#Supported providers

Google, GitHub, Microsoft, Apple, GitLab, LinkedIn, Slack, Twitch, Discord, Facebook, Spotify, Bitbucket, any OpenID Connect provider, and Sign in with Sovaria (use another Sovaria project as the identity provider).

#Connect a provider

1. 1

   Copy the callback URL

   Open Users → Sign in / Providers, choose the provider and copy the callback URL shown there.

2. 2

   Create an OAuth app at the provider

   Paste the callback URL as the authorised redirect URI. Copy the client id and client secret the provider gives you.

3. 3

   Save them in Sovaria

   Paste the client id and secret and turn the provider on. The secret is encrypted and never shown again.

4. 4

   Add your app URL

   Make sure your app's URL is your Site URL or on the redirect list under Users → URL configuration.

#Sign in from your app

// Show buttons for the providers that are turned on
const providers = await sovaria.auth.listProviders()

// Send the browser to the provider
await sovaria.auth.signInWithProvider('google', { redirectTo: 'https://app.example.com/auth/callback' })

// On /auth/callback
const result = await sovaria.auth.handleEmailLink()   // exchanges ?code=…&type=sso for a session
if (result?.type === 'sso' && result.session) goTo('/dashboard')

The flow uses PKCE: the code can only be exchanged by the browser that started the sign-in. Users who sign in with a provider are matched to an existing account by verified email.

#Your project as an identity provider

Under Users → OAuth apps you can let other apps "Sign in with" your project. The other app receives an identity-only token and can read the user's profile from /oauth/userinfo — it never gets access to your data.