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

Support Center

Single Sign On (SSO) with Bime

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

Prerequisites:

  • Generate a public certificate and private key pair.
  • In order to successfully complete the integration between JumpCloud and Bime, you must use an administrator account in Bime.
  • Integration between JumpCloud and Bime also requires the IDP-Initiated URL. This is found at your private Bime sign-in page. Right select Connect and copy the link to your clipboard (it should look something like: https://SUBDOMAIN.bime.io/users/auth/saml?RelayState=PO47YBAgNnib3sw2hSi02SgENdAApGaFbg%2BfqfemE3s%3D).

Notes:

  • How to configure User authorization.
  • SAML 2.0 Just-In-Time (JIT) user provisioning is not supported by Bime.
  • You can upload a service provider application’s XML metadata file to populate SAML 2.0 connector attributes for that application. The attributes populated by the metadata file may vary by 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.

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. In the IDP Entity ID field, enter https://YOURDOMAIN.TLD (e.g., https://thebestwidgets.com).
  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 SUBDOMAIN.bime.io (replace SUBDOMAIN with your Bime subdomain)
  8. In the ACS URL field, enter https://SUBDOMAIN.bime.io/users/auth/saml/callback (replace SUBDOMAIN with your Bime subdomain)
  9. In the IdP-Initiated URL field, paste the link copied from the Bime sign-in page (see Prerequisites above)
  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 under the Service Provider logo within the JumpCloud User console.
  12. Select Activate.

Configure the Service Provider

  1. Log in to Bime as an administrator.
  2. Select the Admin tab (the icon depicting a hammer and screwdriver).
  3. Select the Manage Security Settings tab (the icon depicting a lock).
  4. Leave the box next to Enable BIME authentication checked (at least during testing to prevent account lockout) and check the box next to Enable SAML Authentication.
  5. In the IDP target 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/bime).
  6. In the Certificate finger print field, enter your SHA1 certificate fingerprint.
  7. 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

  • 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:18AM MDT

Related Articles
desk-forwarding@jumpcloud.com
http://assets2.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