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

Support Center

Single Sign On (SSO) with Clarizen

Important: This article contains out-of-date information. For current application information, see Connecting Applications with JumpCloud Using Pre-Built Connectors.



  • How to configure User authorization.
  • We recommend that you allow password authentication as well as single sign-on until you are certain your SSO configuration is working.

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. Select Upload IdP Private Key and upload the private.pem file generated according to the above prerequisites.
  6. In the ACS URL field, enter the value associated with your environment:
  7. EU – https://eu1.clarizen.com/Clarizen/Pages/Integrations/SAML/SamlResponse.aspx
  8. SV – https://app2.clarizen.com/Clarizen/Pages/Integrations/SAML/SamlResponse.aspx
  9. TB – https://app.clarizentb.com/Clarizen/Pages/Integrations/SAML/SamlResponse.aspx
  10. In the field terminating the IdP URL, either leave the default value or enter a plaintext string unique to this connector.
  11. (Optional) In the Display Label field, enter a label that will appear beside the Clarizen logo within the JumpCloud console to guide administrators and users to the connection you have configured.
  12. Select Activate.

Configure the Service Provider

  1. Log in to Clarizen as an administrator.
  2. Select your name in the top navbar, and then select Settings in the dropdown menu.
  3. In the Organization Settings section, select edit... for the field Federated Authentication.
  4. Toggle the Enable Federated Authentication switch to the on position (green).
  5. Select the Upload Certificate button and upload your public certificate generated per the above prerequisites.
  6. In the Sign-in 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/clarizen).
  7. (Optional) If you would like users to be sent back to the JumpCloud User Portal when they log out of Clarizen, enter the following in the Sign-out URL: https://console.jumpcloud.com/userconsole/
  8. Leave the Relaying Partner Identifier at the default value (Clarizen).
  9. In the Enable Password Authentication dropdown, select Everyone (internal and external) (You can change this behavior once you know your SSO configuration is working).
  10. Select Save.

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

  • In your Web browser, navigate to the Clarizen login page.
  • Select Connect via Federated Authentication (If you do not see this link, your browser does not have a linking cookie. Either complete IdP-initiated SSO to create the cookie, or navigate to the To login via SSO URL found on Clarizen's Federated Authentication page.
  • If necessary, log in to the JumpCloud User Portal.
  • You should automatically be logged in to Clarion.

Last Updated: Aug 20, 2019 09:19AM MDT

Related Articles
seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
Invalid characters found