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

Support Center

Single Sign On (SSO) with Adobe Creative Cloud



  • 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.
  • Prior to configuring SSO for Adobe Creative Cloud, you must claim a domain in your Adobe Creative Cloud account and Adobe must approve your claim. The domain for which you wish to configure SSO must show as “Active” in the “Status” column prior to attempting SSO. See Adobe’s article on claiming a domain for more information.
  • Adobe Creative Cloud requires that the IdP public certificate be a .cer file. If you used the above commands to generate a public certificate, rename the file with a .cer extension before uploading it to Adobe Creative Cloud.

Configure the Service Provider

  1. Log in to the Adobe Enterprise Dashboard as an administrator.
  2. Select Identity.
  3. Select Configuration Required for the appropriate domain.
  4. In the Single Sign On Configuration Required section, select Browse and upload your public certificate.
  5. In the IDP Issuer field, enter https://YOURDOMAIN.com (replace YOURDOMAIN with your company’s unique domain).
  6. In the IDP Login URL field, enter https://sso.jumpcloud.com/saml2/adobecreativecloud (this is the default IdP URL, but if you plan to change this value in JumpCloud, then provide your chosen value).
  7. Beside IdP Binding, select HTTP - Post from the drop-down menu.
  8. Beside User Login Setting, select Email address from the drop-down menu.
  9. Select Save.
  10. Select Download metadata and open the metadata file that saves to your computer.
  11. Select Activate Federated ID.

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. From Adobe’s metadata file that you downloaded, copy the entityID attribute value of the EntityDescriptor element and paste this value in the SP Entity ID field in JumpCloud (this value should look something like: https://www.okta.com/saml2/service-provider/ID_NUMBER).
  7. From Adobe’s metadata file that you downloaded, copy the location attribute value of the AssertionConsumerService element and paste this value in BOTH the ACS URL AND the IdP-Initiated URL fields (this value should look something like: https://adbe-IDENTIFIER.okta.com/auth/saml20/accauthlinktest).
  8. In the field terminating the IdP URL, either leave the default value or enter a plaintext string unique to this connector.
  9. (Optional) In the Display Label field, enter a label that will appear under the Service Provider logo within the JumpCloud User console.
  10. Select Activate.

Validate SSO authentication workflows

IdP Initiated

  • Adobe does not currently support IdP initiated log in

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:43PM MDT

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