Skip to main content

Set up single sign-on (SSO) with another OpenID Connect provider

J
Written by JP Arredondo

Before setup

Ask your Sana contact for the redirect URI of your Sana workspace.


Setup

Use this article for an identity provider that doesn't have its own article, such as Auth0, Keycloak, Ping or a self-hosted issuer. For Microsoft Entra ID, Google Workspace and Okta, see Set up single sign-on (SSO) with Microsoft Entra ID, Set up single sign-on (SSO) with Google Workspace and Set up single sign-on (SSO) with Okta.

You supply the issuer URL; everything else works the same as for those providers. The redirect URI is specific to your Sana workspace, so you need one registration per Sana workspace.

1. Register the client

  • Create a confidential (server-side / "web") client that supports the authorization code grant and issues a client secret. A public / SPA client cannot be used.

  • Make sure openid, profile and email are grantable. Those are exactly the scopes Sana requests.

  • Add the redirect URI from your Sana contact to the client's allow-list, exactly as you received it, with no trailing slash. It looks like this:

    • EU workspaces: https://sana-eu.myworkday.com/x-api/<workspace ID>/auth/oidc/callback

    • US workspaces: https://sana.myworkday.com/x-api/<workspace ID>/auth/oidc/callback

2. Find the issuer

The issuer is the base URL serving <issuer>/.well-known/openid-configuration, and the issuer value inside that document must equal it.

Sana enforces that equality, which is where most first attempts fail: consoles often show a login URL or an authority URL instead. Fetch the metadata document and copy its issuer verbatim. Sending Sana the full /.well-known/openid-configuration URL is also fine; Sana strips it.

The document, and the endpoints it advertises, must be reachable by Sana over HTTPS on a public address, without redirects, within 5 seconds.

3. Check the email claim (required)

The ID token must carry an email claim. Without it, the user signs in at your identity provider and is then rejected by Sana with error EMAIL_MISSING. Sana does not fall back to preferred_username and never calls the userinfo endpoint. Some providers include it with the email scope; others need a claim mapping.


After setup

Send your Sana contact:

  • Sign-in button name: the label your users see on the Sana sign-in page, for example "Sign in with Keycloak".

  • Issuer URL (from step 2).

  • Client ID and Client secret (from step 1).

Your Sana contact will tell you how to share the client secret securely; don't send it in a regular email or chat message.

Did this answer your question?