[IMPORTANT] Please note that this site will be disabled on October 31. In it's place, the new JumpCloud Help Center is live! Check it out here!

Support Center

Single Sign On (SSO) with Assembla

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.
  • SAML 2.0 Just-In-Time (JIT) user provisioning is supported by Assembla.
  • Once a portfolio manager has saved the SSO configuration in Assembla, users (and the administrator) will only be able to sign in via SSO. To prevent account lockout during testing, we recommend that the configuring manager sign in to Assembla in a browser separate from the one in which he or she will complete testing. If the SSO configuration fails, the manager will still have access to the account in the other browser and can modify or disable the configuration.

Configure the Service Provider: Part 1

  1. Log in to Assembla using an account with “Manager” permissions.
  2. Navigate to your portfolio Admin page located at https://SUBDOMAIN.assembla.com/p/admin (replace SUBDOMAIN with your Assembla portfolio name).
  3. In the SAML Authentication section, check the box next to Enable.
  4. Copy the SAML Assertion Consumer Service URL.
  5. Leave the Assembla 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. Select Upload IdP Private Key and upload the private.pem file generated according to the above prerequisites.
  6. Select Upload IdP Certificate and upload the cert.pem file generated according to the above prerequisites.
  7. In the SP Entity ID field, enter https://SUBDOMAIN.assembla.com/p/home (replace SUBDOMAIN with your Assembla portfolio name).
  8. In the ACS URL field, paste the SAML Assertion Consumer Service URL you copied from the Assembla configuration page.
  9. In the field terminating the IdP URL, either leave the default value or enter a plaintext string unique to this connector.
  10. (Optional) In the Display Label field, enter a label that will appear under the Service Provider logo within the JumpCloud User console.
  11. Select Activate.

Configure the Service Provider: Part 2

  1. Back in Assembla, in the Identity Provider 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/assembla).
  2. In the X509 Certificate field, paste the contents of your public certificate.
  3. Select Update SAML settings.

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 20, 2019 09:17AM MDT

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