Skip to Content

Single sign-on

Add a SAML identity provider

Connect Okta, Microsoft Entra ID or any SAML 2.0 provider to Databrain.

Before you start

  • Your company is on the Enterprise plan.
  • Enable SSO is on. See Set up single sign-on.
  • You can create a SAML app in your identity provider.

Steps

  1. Go to Settings > Security, select the SSO tab, then select Add identity provider.

    SSO tab with Enable SSO on and the Add identity provider button highlighted above the providers table.
    Add identity provider appears once Enable SSO is on.
  2. Set Provider type to SAML.

    New identity provider dialog with the Provider type select highlighted, set to SAML.
    Choose SAML or OIDC first. The form changes with it.
  3. Enter an Alias, for example okta. You cannot change it later.

  4. Copy the two values under Databrain endpoint into your identity provider’s SAML app:

    SAML form with the Redirect URI field highlighted under Databrain endpoint, then SP entity ID, Alias okta and Display name Okta.
    Copy the Redirect URI and SP entity ID into your identity provider.
    • Redirect URI: the single sign-on (ACS) URL.
    • SP entity ID: the audience, Databrain-<alias>.
  5. In your identity provider, set the NameID format to email address, and assign the users who may sign in.

  6. Back in Databrain, fill in Provider details from your identity provider’s SAML app:

    • Display name: the name your team sees.
    • Idp entity ID: the issuer.
    • SSO URL: the sign-in URL.
    • Logout URL: the sign-out URL.
  7. Select Download signature certificate and upload it to your identity provider if it asks for a signing certificate.

  8. Select Create IDP.

    Bottom of the New identity provider dialog with the Create IDP button highlighted next to Download signature certificate.
    Create IDP saves the provider. Activate it from the table.
  9. In the providers table, select Activate.

The provider shows Active. Test it with one user: sign out, then use Continue with SSO.

Databrain matches the user by the email in the SAML response. The email must match an existing Databrain user.

In the providers table, Metadata has a Copy button and Signature certificate has a Download button for later use.

If something goes wrong

  • The SAML option refuses to save. SAML needs the Enterprise plan.
  • Please use the invited email id. The email in the SAML response is not the one the user entered. Check the NameID mapping.

On this page