[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 WebEx



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. Select Upload IdP Private Key and upload the private.pem file generated according to the above prerequisites.
  7. Select Upload IdP Certificate and upload the cert.pem file generated according to the above prerequisites.
  8. In the ACS URL field, enter https://SUBDOMAIN.webex.com/dispatcher/SAML2AuthService?siteurl=SUBDOMAIN (replace SUBDOMAIN with your WebEx subdomain).
  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.
  12. Select export metadata in the WebEx application entry

Configure the Service Provider

  1. Log in to WebEx Site Administration as an administrator (https://SUBDOMAIN.webex.com/admin -- replace SUBDOMAIN with your WebEx subdomain)
  2. Select on the Configuration in the sidebar
  3. Mouse over Common Site Settings in the sidebar, then select SSO Configuration from the context menu
  4. In the Federation Protocol dropdown, select SAML 2.0
  5. Select the SP Initiated radio button
  6. Select the Import SAML Metadata link, and upload the metadata file exported from Step 11 under JumpCloud SSO Application configuration
  7. Leave the WebEx SAML Issuer (SP ID) field set to http://www.webex.com
  8. In the Issuer for SAML (IdP ID) field, enter the value from Part 1, Step 4 above
  9. In the Customer SSO Service Login 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/webex)
  10. In the NameID Format dropdown, select Email address
  11. Leave the AuthnContextClassRef field, leave the default value of urn:oasis:names:tc:SAML:2.0:ac:classes:PasswordProtectedTransport
  12. Enter a desired WebEx target URL in the field Default WebEx Target page URL (ex: https://SUBDOMAIN.webex.com/mw3000/mywebex/default.do?siteurl=SUBDOMAIN)
  13. (Optional) If you would like users to be sent back to the JumpCloud User Portal when they log out of WebEx, select the Single Logout checkbox, then enter the following in the Customer SSO Service Logout URL: https://console.jumpcloud.com/userconsole/
  14. Select the Update button

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.
  • Select on Log In in the upper-right corner
  • 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: May 15, 2019 11:02AM MDT

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