Google OIDC

You'll learn how to register redirect URIs in Google Cloud and create the connection in SqlOS.

Redirect URI#

The default hosted provider callback path is:

https://your-app.example.com/sqlos/auth/oidc/callback

For local development with the default SqlOS base path:

http://localhost:5062/sqlos/auth/oidc/callback

Create the OIDC connection in SqlOS first, then copy the dashboard callback URI into Google Cloud.

Google Cloud setup#

1. Open Google Cloud Console.
2. Create or select a project and configure the OAuth consent screen.
3. Create an OAuth client ID (Web application).
4. Add the SqlOS callback URI from the dashboard.
5. Copy the client ID and client secret.

SqlOS dashboard setup#

1. Open /sqlos/admin/auth/oidc on your running app.
2. Create a connection:
   • Provider: Google
   • Display name: shown on the login button
   • Client ID and client secret from Google
3. Save, then update Google's redirect URIs with the exact callback shown by the dashboard.
4. Confirm the connection is enabled. Newly created API/dashboard connections are enabled by default; the toggle is useful after an operator disables one.

Default scopes when left empty: openid, email, profile.

API setup (optional)#

curl -X POST http://localhost:5062/sqlos/admin/auth/api/oidc-connections \
  -b "$SQLOS_DASHBOARD_COOKIE_JAR" \
  -H "Content-Type: application/json" \
  -d '{
    "providerType": "google",
    "displayName": "Google",
    "clientId": "YOUR_CLIENT_ID.apps.googleusercontent.com",
    "clientSecret": "YOUR_CLIENT_SECRET",
    "allowedCallbackUris": [
      "http://localhost:5062/sqlos/auth/oidc/callback"
    ]
  }'

The create operation enables the connection. Use the following endpoint only to re-enable a connection that was disabled:

curl -X POST http://localhost:5062/sqlos/admin/auth/api/oidc-connections/{id}/enable \
  -b "$SQLOS_DASHBOARD_COOKIE_JAR"

See Authenticate operator API calls before using any admin curl example.

Test#

1. Open your app login or /sqlos/auth/login.
2. Enter an email and choose Continue with Google.
3. Complete Google sign-in and confirm your app receives tokens.

Common failures#

Next steps#

• OIDC overview
• Microsoft OIDC
• Troubleshooting