[Notification] We're upgrading the JumpCloud Support Center the week of September 30th.

Support Center

Single Sign On (SSO) with Domo

Prerequisites:

Notes:

  • After you connect an application to JumpCloud, you can connect it to user groups. Users in the groups you connect can access the application through SAML SSO. Learn how to connect user groups to applications.
  • SAML 2.0 Just-In-Time (JIT) user provisioning is supported by Domo.
  • After configuring and saving the single sign-on configuration in Domo, the administrator and all users will only be able to sign in via SSO. If the SSO configuration fails during testing, Domo administrators may still sign in by going to https://SUBDOMAIN.domo.com/auth/index?domoManualLogin=true.
  • In order to upload your certificate while configuring Domo for SSO, your certificate needs to bear a .cer file extension. If you generated your certificate using the command above, duplicate it and rename it with the .cer extension.

Configure the Service Provider: Part 1

  1. Log in to Domo as an administrator.
  2. Navigate to your Domo Admin portal located at https://SUBDOMAIN.domo.com/admin.
  3. Select on Security.
  4. Select on Single Sign-On.
  5. Select Enable Single Sign-On.
  6. Copy the SAML Assertion Endpoint URL.
  7. Leave the Domo configuration page open.

Configure the JumpCloud SSO Application

  1. Access the JumpCloud Administrator Console at https://console.jumpcloud.com.
  2. Select Applications in the main navigation panel.
  3. Select the + in the upper left, scroll or search for the application in the 'Configure New Application' side panel, the select 'configure'.
  4. You can upload a service provider application's XML metadata file to populate SAML connector attributes for that application. The attributes populated by the metadata file may vary by the application. To apply a metadata file for the application you're connecting, click Upload Metadata. Navigate to the file you want to upload, then click Open. You'll see a confirmation of a successful upload. Be aware that if you upload more than one metadata file, you'll overwrite the attribute values applied in the previously uploaded file.
  5. In the IDP Entity ID field, enter https://YOURDOMAIN.TLD (e.g., https://thebestwidgets.com).
  6. In the ACS URL field, paste the SAML Assertion Endpoint URL you copied from the Domo configuration page (ex: https://SUBDOMAIN.domo.com/auth/saml)
  7. In the field terminating the IdP URL, either leave the default value or enter a plaintext string unique to this connector.
  8. (Optional) In the Display Label field, enter a label that will appear under the Service Provider logo within the JumpCloud User console.
  9. Select Activate.

Configure the Service Provider: Part 2

  1. Back in Domo, in the Identity Provider Endpoint URL field, enter the same IdP URL that you set in the JumpCloud console (if you did not modify the termination of this URL, then enter the default URL: https://sso.jumpcloud.com/saml2/domo).
  2. In the Entity ID field, enter ‘Domo’.
  3. Under X.509 Certificate, select the arrow icon and upload your public certificate.
  4. Leave Import groups from identity provider unchecked.
  5. Check Only invited people can access Domo if you want to disable JIT user provisioning.
  6. Select Save Changes.

Validate SSO authentication workflows

IdP Initiated

  • Access the JumpCloud User Console at https://console.jumpcloud.com.
  • Select the Service Provider icon.
  • This should automatically launch and login to the application.

SP Initiated

  • Navigate to your Service Provider application URL.
  • You will be redirected to log in to the JumpCloud User Portal.
  • The browser will be redirected back to the application and be automatically logged in.
 

Last Updated: Aug 19, 2019 01:08PM MDT

Related Articles
desk-forwarding@jumpcloud.com
https://cdn.desk.com/
false
desk
Loading
seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
about
false
Invalid characters found
/customer/en/portal/articles/autocomplete