Single Sign-On
  • 28 May 2024
  • 1 Minute to read
  • PDF

Single Sign-On

  • PDF

Article summary

This article will describe the information and steps needed in order to set up Single Sign-On (SSO) Authentication with Bobsled using SAML 2.0.

Single Sign-On lets your users sign in just one time to get access to all your organisation's applications.

High-Level Overview:

Supported Providers 

Below is a list of SAML Single Sign-On providers we currently integrate with. 

  • Okta Single Sign-On
  • Microsoft Azure Active Directory
  • Google Authentication
  • JumpCloud

If your provider of choice is not listed below but supports SAML 2.0, please contact us and we can work with you on configuration.

Configuring Single Sign-On 

We will provide the following information for your configuration:

  • Bobsled Entity ID: The URI that identifies Bobsled to your idP. 
    The Bobsled Entity ID will be the same as your environment URL i.e. {environment_name}

To set up SSO, we will need the following information from your organisation:

  • idP Entity ID: The URI that identifies your identity provider
  • idP SAML SSO URL: The URL of your identity provider’s sign-in page that your users visit
  • idP public key certificate: The public certificate used to validate tokens signed by your identity provider

With the following information, please get in touch with your account representative or raise a ticket here to configure SSO.

Setting Up Users for Single Sign-On

To grant your users access to log in using your SSO provider, you will need to create a user by inviting and assigning a role to them in Bobsled. 

For more information on creating users, roles and permissions, please refer to this article: Creating and Inviting Users.

Was this article helpful?

What's Next