Skip to main content

How to configure Single Sign On (SSO)

Enable SSO so that your organization's users can sign in to Databook easily and securely

Written by Alex

Overview

Databook supports SSO and encourages all customers to use it, to increase the ease and security with which users can sign into Databook.

Please contact your Databook account manager if you need any help setting up SSO for your organization.


Supported Features

Supported protocols

SAML 2.0

IdP-initiated SSO

Identity Provider-initiated Single Sign-On. A single sign-on operation that was started from the IdP Security Domain (Okta, Salesforce, AWS Federated, etc.). The IdP federation server creates a federation SSO response and redirects the user to the SP (Databook) with the response message.

SP-initiated SSO

Service Provider-initiated Single Sign-On. SAML authentication that is initiated by the Service Provider (SP) i.e. Databook. This is triggered when the end user tries to access a resource in Databook or sign in directly to Databook.


Configuration Steps

Step 1: Contact your Databook support team and request that they enable SAML 2.0 SSO for your Organization.

You will also need to work with your Databook support team to decide on a unique identifier for your SAML connection.This will be used to generate the ACS URL, Entity ID, and optionally the SP-initiated flow URL.

The connection identifier should be unique to your organization and/or environment and must satisfy these requirements: Must start and end with an alphanumeric character and can only contain alphanumeric characters and '-'. Max length 128. e.g. databook-staging or databook.

Step 2: Once the connection identifier has been decided, configure the following values in the IDP.

  • Assertion Consumer Service URL (ACS URL): https://databook.auth0.com/login/callback?connection=<IDENTIFIER>

  • Entity ID: urn:auth0:databook:<IDENTIFIER>

  • (Optional) SP-initiated flow URL: https://databook.auth0.com/login?client=[client-id]*&connection=<IDENTIFIER.> If this is required, request the [client-id] from your Databook support team.

  • (Recommended) Subject Type: User ID

  • (Recommended) Name ID Format: urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress

  • (Required) SAML Attributes:

    • firstName

    • lastName

    • email

  • (Optional) SAML Attributes

    • groupTag (This should be the group or organizational unit the user belongs to - this will help us segment users in Databook

Step 3: (Optional) Download Databook certificate

If your Organization requires signed and/or encrypted SAML requests, the Databook certificate can be downloaded from here: https://databook.auth0.com/pem?cert=connection

Step 4: Provide X509 Signing Certificate and Signin URL to Databook

Now that the IDP has been configured, Databook requires a X509 Signing Certificate and a Sign In URL to complete the SSO connection setup.

There are 3 ways this can be provided:

  • (Recommended) Provide your Databook support team with a SAML Metadata URL. This can usually be found within the IDP configuration. This approach is recommended because Databook can automatically retrieve a new X509 Signing Certificate upon expiration.

  • Provide a SAML Metadata XML file. This will contain the required data needed to complete the connection.

  • Directly provide the X509 Signing Certificate and Sign In URL.

Step 5: Test the SSO login

After your Databook support team has completed the setup, the SSO connection will be established. All users with your Organization’s email address will now be able to seamlessly login to Databook.

If your Organization is using SP-initiated SSO

(1) Navigate to the Databook platform homepage

(2) Enter your email address

(3) Click “Sign In”

(4) You will now be redirected to the IDP to login

(5) After login you will be redirected back to Databook

If your Organization is using IdP-initiated SSO

(1) Login to your IDP

(2) Click the Databook tile

(3) You will now be redirected to Databook

Please contact your Databook account team if you have any custom configuration requirements for SSO.

Did this answer your question?