SSO

17min

Installation

You can setup this integration as a logged in admin user in the integrations page:

Document image


Identity Providers

Rootly is compatible with any identity provider supporting SAML 2.0.

Depending on the identity provider, you might be asked for the following information during your setup process:

ACS URL: https://rootly.com/users/saml/auth Entity ID: https://rootly.com/users/saml/metadata

Okta

Let's go to the Applications panel.

Document image




Search for Rootly.

Document image




Click on Add.

Document image




Select SAML 2.0.

No our app is created let's go back in Applications > Rootly and click View Setup Instructions:

Document image




Finally copy the fields as shown below into Rootly, this information from Okta is unique to your organization.

Document image




You are all set !

Google

You will need to access the Google Admin Console: https://admin.google.com/ac/home.

Follow screenshot steps as below:

Document image




Document image




Document image




Document image

Document image


Make sure Signed Response is checked and the app ON for everyone is checked in your org unit.

Document image


And finally let's edit the attributes mapping.

Document image


Let's switch to Rootly. You can get the identity login url by clicking on the TEST SAML LOGIN button.

Document image

Document image


OneLogin

Browse the Applications Store page and install Rootly.

Document image




Copy fields over Rootly like shown below

  • Issuer URL -> Identity Provider ID
  • SAML 2.0 endpoint -> Identity Login Url
  • In the certificate section > View Details > X.509 Certificate -> Idp Cert
Document image




You are all set !

Auth0

Azure

Install SSO integration through the Azure marketplace

Rippling

Integrate Rippling SSO + SCIM in one click https://www.rippling.com/app-shop/app/rootly

Document image


Jumpcloud

Let's begin by navigating to the SSO Applications page from the left navigation.

Document image


Search for and install the Rootly application.

Document image


Once installed, select the Rootly application to enter edit mode and navigate to the SSO tab.

Update the IdP Entity ID from JumpCloud to JumpCloud-<BusinessName>.

Document image


Download your IDP Certificate. It should download as a .pem file.

Document image


Navigate to your Rootly SSO Integration modal and fill in the following fields with the corresponding values from JumpCloud.

Document image


Rootly Field

JumpCloud Field

Identity Provider Id

IdP Entity ID

Identity Login Url

IDP URL

Identity Logout Url

Leave blank or choose any page you'd want to navigate your user to when they log out.

Idp Cert

Open the certificate you downloaded in the previous step with a text editor of your choice. Copy and paste the text content.

Domain Name

Your domain (e.g. mycompany.com)

Go ahead Enable and Save your SSO setup in Rootly.

Document image


You're now SSO enabled!

If you want to set up Just-In-Time (JIT) provisioning, navigate to the Identity Management tab in edit mode and set the following fields according to the mappings below.

Document image

  • API Type: SCIM API
  • SCIM Version: SCIM 2.0
  • Base URL: https://rootly.com/scim
  • Token Key: Pick this value up from your SSO Configuration screen in in Rootly
Document image

  • Test User Email: You can use your own email as long as the email domain matches the one set in your Rootly SSO configuration page.

Go ahead and select Test Connection. You should see a successful message once a connection is confirmed.

If you'd like to provision users by JumpCloud Groups, go ahead and select the following option.This will allow you to provision the users in each JumpCloud Group with a specific Rootly Role.

Document image


Navigate to your Rootly SSO Integrations modal and map the desired JumpCloud Group to the desired Rootly Role.

Document image


Go ahead and Save your configuration. You're all set for JIT user provisioning!

Login Behaviour

If you have SSO enabled, all other login methods such as Google, Slack, Email/Password will automatically redirect users to the SSO method instead.

Misconfiguration

If you set up SSO incorrectly, you may not be able to sign in anymore. In that case please contact [email protected] or use the lower right chat widget for live assistance.

Support

If you need help or more information about this integration, please contact [email protected] or use the lower right chat widget to get connected with an engineer.

Updated 19 Sep 2024
Doc contributor
Doc contributor
Doc contributor
Doc contributor
Doc contributor
Did this page help you?