Skip to main content
With SAML single sign-on (SSO), your users sign in to Qobra with the account of your identity provider (IdP), such as Okta, Microsoft Entra ID or Keycloak. Your IdP checks who they are, applies your own rules (password policy, multi-factor authentication) and sends them back to Qobra signed in. Qobra implements SAML 2.0, and the feature is pen-tested every year by independent contractors.
SAML SSO is available from the Advanced pack. Setting it up requires a role with Security: Can edit in its company settings permissions, and admin access to your identity provider.
SSO signs users in: it doesn’t create them. Add them in Qobra, or let your identity provider create them with SCIM provisioning.

Set up SAML SSO

1

Turn on SAML SSO in Qobra

In Settings > Security, turn on 1 SAML SSO. The Configure SAML SSO dialog opens. Later, reopen it with 2 Edit SAML SSO configuration.
The Log in card of Settings > Security, with 1 the SAML SSO switch turned on and 2 the Edit SAML SSO configuration button
2

Copy the Qobra values into your identity provider

In your identity provider, create a SAML 2.0 application for Qobra and paste the two values of the dialog, with their copy buttons:
  • 1 Entity ID: the identifier of your Qobra account, also called Audience URI or Identifier.
  • 2 Redirect URL: where your identity provider sends users back once they are authenticated, also called Single sign-on URL, Reply URL, ACS URL or Callback URL.
Set the Name ID format to email, and sign the assertions. The tutorials below give the steps for Okta, Microsoft Entra ID and Keycloak.
The Configure SAML SSO dialog with 1 the Entity ID and 2 the Redirect URL to copy, 3 the Metadata URL and 4 the Domain name to fill in
3

Paste your identity provider's metadata URL in Qobra

Back in Qobra, fill in:
  • 3 Metadata URL: the public URL of your identity provider’s SAML metadata, an XML document with its endpoints and signing certificate.
  • 4 Domain name: the domain of your users’ work emails. It is filled in with the domain of your own email. To add another domain, after a merger or a rebranding for example, contact support@qobra.co: for security, you can’t add one yourself.
Click Save. Qobra checks the metadata URL before saving it.
4

Test the connection

Open a private browsing window, go to https://app.qobra.co/auth and click Log in with SSO. Enter an email of your domain: you should go through your identity provider and land in Qobra. Keep your current session open until the test succeeds.
Once SSO works, you can turn off Password in Settings > Security, so that every sign-in goes through your identity provider. With password off, Qobra sends users of your domain to your identity provider as soon as they enter their email. See Sign-in methods and sessions. The SP metadata URL of the dialog is for identity providers that require encrypted assertions. If you need encryption, ask your Qobra contact to generate the certificates.

What the metadata looks like

The metadata URL must return an XML document like this one:

Identity provider tutorials

Step-by-step setups for the identity providers our customers use the most. To see another one here, write to support@qobra.co.
  1. In the Okta Admin Console, go to Applications and click Create App Integration. Select SAML 2.0.
    The Create a new app integration dialog of Okta with SAML 2.0 selected
  2. Fill in the general settings: name the app Qobra and add its logo if you like.
    The General Settings step of the Okta app integration, with Qobra as the app name
  3. Fill in the SAML settings as shown below: Single sign-on URL is the Qobra Redirect URL and Audience URI is the Qobra Entity ID. Your IT team may require advanced settings of its own.
    The SAML Settings step of the Okta app integration
  4. Finish the setup.
    The last step of the Okta app integration
  5. Copy the metadata URL of the app and paste it in the Qobra Metadata URL field.
    The metadata URL of the Qobra app in Okta
  6. Assign the people or groups who sign in to Qobra to the app.
  1. Go to Enterprise applications and click New application.
    The Enterprise applications page of Microsoft Entra ID with the New application button
  2. Select the Microsoft Entra SAML Toolkit application, name it Qobra and click Create.
    The Microsoft Entra SAML Toolkit in the application gallery
  3. In the new application, open Single sign-on and select SAML.
    The Single sign-on tab of the application with the SAML method
  4. Click Edit to fill in the SAML data.
    The Basic SAML Configuration section with its Edit button
  5. Fill in the three fields with the values of the Qobra Configure SAML SSO dialog, then click Save:
    • Identifier (Entity ID): the Qobra Entity ID;
    • Reply URL: the Qobra Redirect URL;
    • Sign on URL: https://app.qobra.co/auth.
    The Basic SAML Configuration form with the identifier, the reply URL and the sign on URL filled in
  6. In SAML Certificates, copy the App Federation Metadata Url and paste it in the Qobra Metadata URL field.
    The SAML Certificates section with the App Federation Metadata Url
  7. In Users and groups, assign the people or groups who sign in to Qobra.
  1. In the administration console, add a client of type SAML.
    The Create client form of Keycloak
  2. Go to the next step and fill in the login settings as shown below.
    The Login settings step of the Keycloak client
  3. Once the client is created, set these options:
    • Sign assertions: on
      The Sign assertions option turned on in the Keycloak client
    • Name ID format: email
      The Name ID format option set to email in the Keycloak client
    • Client signature required, in the Keys tab: off
      The Keys tab of the Qobra client in Keycloak, with Client signature required turned off
  4. Copy the metadata URL and paste it in the Qobra Metadata URL field.
    The SAML metadata URL in Keycloak

Troubleshooting

Okta, Microsoft Entra ID and Keycloak each give a metadata URL: see the tutorials above. If your identity provider only lets you download the metadata file, serve it from a public URL (cloud storage, static server): Qobra doesn’t accept a metadata file upload.
Qobra must reach the URL from the internet. A URL that points to your internal network, such as a self-hosted identity provider, is blocked for security. Serve the metadata from a public URL.
Open the metadata URL in your browser. It must return an XML document, not an error, and the assertions must be signed. Check that the user is assigned to the Qobra application in your identity provider and exists in Qobra with the same email.
For security, the domain name must match the domain of the admin who sets up SSO, and public email domains such as gmail.com or outlook.com are refused. To use another domain or add a second one, contact support@qobra.co.