Integrate with Cisco Webex

Use JumpCloud SAML Single Sign On (SSO) to give your users convenient but secure access to all their web applications with a single set of credentials. Automatically provision, update and deprovision users in Cisco Webex from JumpCloud using the Identity Management (SCIM) integration. Leverage this integration to centralize user lifecycle, user identity, and group management in JumpCloud for Cisco Webex. Save time and avoid mistakes, as well as potential security risks, related to manually creating users.

Read this article to learn how to setup the Cisco Webex integration.

Prerequisites

  • A JumpCloud Administrator account.
  • A Cisco Webex user account with administrator permissions.
  • Your Cisco domain and ID.
  • SAML SSO must be enabled.

Important Considerations

  • Cisco Webex SCIM API is based on version 2.0 of the SCIM standard.
  • Groups are not supported.
  • The following operations are supported for users:
    • Create users
    • Deactivate users
    • Update users

Attribute Considerations

  • A default set of attributes are managed for users. See the Attribute Mappings section for more details.

Creating a new JumpCloud Application Integration

  1. Log in to the JumpCloud Admin Portal.
  2. Navigate to USER AUTHENTICATION SSO Applications.
  3. Click + Add New Application.
  4. Type the name of the application in the Search field and select it.
  5. Click Next.
  6. In the Display Label, type your name for the application. Optionally, you can enter a Description, adjust the User Portal Image and choose to hide or Show in User Portal.

Note:

If this is a Bookmark Application, enter your sign-in URL in the Bookmark URL field.

  1. Click Save Application.
  2. If successful, click:
    • Configure Application and go to the next section.
    • Close to configure your new application at a later time.

Configuring the SSO Integration

To configure JumpCloud

  1. Create a new application or select it from the Configured Applications list.
  2. Select the SSO tab.
  3. Replace any instances of YOUR_SUBDOMAIN and YOUR_ID with the appropriate values.
  4. Add any other changes and click save.
  5. Find Cisco Webex in the list of applications and click anywhere in the row to open it.
  6. Select the SSO tab and click Export Metadata.

To configure Cisco Webex

  1. Log in to WebEx Site Administration as an administrator.
  2. Select on the Configuration > Common Site Settings > SSO Configuration.
  3. In the Federation Protocol dropdown, select SAML 2.0
  4. Select the Site Certificate Manager link.
  5. In the Site Certificate Manager window, select Browse, and then navigate to the location of the JumpCloud Metadata file you exported in the previous section.
  6. Select the XML file, and then select OK.
  7. Select Close.
  8. Enter the required information on the SSO Configuration page and select the options you want to enable.

Webex SSO Configuration Page Fields and Options

Field or Option Description
AuthnContextClassRef The SAML statement that describes the authentication at the IdP. This must match the IAM configuration. ADFS examples: urn:federation:authentication:windows or urn:oasis:names:tc:SAML:2.0:ac:classes:PasswordProtectedTransport Ping example: urn:oasis:names:tc:SAML:2.0:ac:classes:unspecified  To use more than one AuthnContextClassRef value add a ";".For example: urn:federation:authentication:windows;urn:oasis:names:tc:SAML:2.0:ac:classes:PasswordProtectedTransport
Auto Account Creation (optional) Select to create a user account. UID, email, and first and last name fields must be present assertion.
Auto Account Update (optional) Webex accounts can be updated with the presence of an updateTimeStamp attribute in t When modifications are made in the IdP, the new timestamp is sent to the Webex site, w account with any attribute sent in the SAML assertion.
Customer SSO Error URL (optional) If an error occurs, redirects to this URL with the error code appended in the URL.
Customer SSO Service Login URL URL for your enterprise's single sign-on services. Users typically sign in with this URL. Located in the IdP XML file (example: )
Default Webex Target page URL (optional) Upon authentication, displays a target page assigned for the web application only.
Import SAML Metadata (link) Click to open the Federated Web SSO Configuration - SAML Metadata dialog box. Imported metadata fields include the following:AuthnRequestSigned DestinationIssuer for SAML (IdP ID)Customer SSO Service Login URL
Issuer for SAML (IdP ID) A URI uniquely identifies the IdP. The configuration must match the setting in the Customer IAM. Located in the IdP XML file (example: entityID=" http://adfs20-fed-srv.adfs.webexeagle.com/adfs/services/trust")
NameID Format Must match the IdP configuration, with the following formats being supported:UnspecifiedEmail addressX509 Subject NameEntity IdentifierPersistent Identifier
Remove uid Domain Suffix for Active Directory UPN Removes the Active Directory domain from the User Principal Name (UPN) when selected.
SSO Profile Specify how users access the Webex site. Select SP Initiated if users start at the Webex meeting site and are redirected to the corporate IdP system for authentication. Select IdP Initiated if users access the Webex site through the corporate IAM system.
SSO authentication for Attendees This feature provides additional levels of accountability to the SAML assertion user authentication for internal attendees using Webex Meetings, Webex Training, and Webex Events. When enabled, this feature supersedes the Webex Meetings "Display internal user tag in participant list" feature.
Signature Algorithm for AuthnRequest For enhanced security, you can now generate SHA-1, SHA-256, or SHA-512 signed certificates.
Single Logout (optional) Check to require a sign-out and set the logout URL.  IdP initiated Single Logout is not supported.
Webex SAML Issuer (SP ID) The URI identifies the Webex Messenger service as an SP. The configuration must match the settings in the customer Identity Access Management system. Recommended naming conventions: For Webex Meetings, enter the Webex Meetings site URL. For the Webex Messenger service, use the format "client-domain-name" (example: IM-Client-ADFS-WebexEagle-Com).
You can export a SAML metadata Webex configuration file You can export some metadata, which can then be imported in the future. Exported metadata fields include the following:AuthnRequestSigned DestinationIssuer for SAML (IdP ID)Customer SO Service Login URL
  1. Select the Update button.

Authorizing User SSO Access

Users are implicitly denied access to applications. After you connect an application to JumpCloud, you need to authorize user access to that application. You can authorize user access from the Application Configuration panel or from the Groups Configuration panel. 

To authorize user access from the Application Configuration panel

  1. Log in to the JumpCloud Admin Portal.
  2. Go to USER AUTHENTICATION > SSO Applications, then select the application to which you want to authorize user access.
  3. Select the User Groups tab. If you need to create a new group of users, see Get Started: User Groups.
  4. Select the check box next to the group of users you want to give access.
  5. Click save

To learn how to authorize user access from the Groups Configuration panel, see Authorize Users to an SSO Application.

Validating SSO authentication workflow(s)

IdP Initiated

  • Access the JumpCloud User Console.
  • Select the application’s tile.
  • The application will launch and login the user.

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.

Configuring the Identity Management Integration

To configure Cisco Webex

  1. Get your organization ID from the customer view in the Control Hub:
    • Log into Cisco Webex.
    • Click your organization name on the bottom left.
    • Copy the Organization ID into a text file. You need this value when you enter the tenant URL. 
  2. Get the bearer token value for the Secret Token:

Important:

An incognito browser is important to make sure you sign in with the correct admin credentials. If you’re already signed in as a less privileged user who can't create users, the bearer token that you return can't create users.

  1. ​​​​From the Webex sign in page that appears, sign in with a full admin account for your organization.
  2. An error page appears saying that the site can’t be reached, but this is normal.
  3. The error page’s URL includes the generated bearer token. This token is valid for 365 days (after which it expires).
  4. From the URL in the browser’s address bar, copy the bearer token value from between access_token= and &token_type=Bearer. For example, this URL has the token value highlighted: http://localhost:3000/auth/code#access_token={sample_token}&token_type=Bearer&expires_in=3887999&state=this-should-be-a-random-string-for-security-purpose.
  5. Save this value in a text file as a record of the token in case the URL isn’t available any more.

To configure JumpCloud

  1. Create a new application or select it from the Configured Applications list.
  2. Select the Identity Management tab.
  3. Click Configure.
  4. You are presented with two fields:
    • *Base URL:
      • If using Webex (default) – enter https://api.ciscospark.com/v1/scim/{org_id}
      • If using Webex for Government – enter https://api-usgov.webex.com/v1/scim/{org_id}
        • Replace {org_id} with your organization’s ID
    • Token Key: Paste the bearer token value you generated in the previous section.
  5. Click Activate and then save.
  6. You will receive a confirmation that the Identity Management integration has been successfully verified.

Attribute Mappings

The following table lists attributes that JumpCloud sends to the application. See Attribute Considerations for more information regarding attribute mapping considerations. 

Learn about JumpCloud Properties and how they work with system users in our API

Cisco Webex User Attributes

JumpCloud Property JumpCloud UI Field Name SCIM v2 Mapping Cisco Webex Value
username Username userName email
active status active active
displayname Display Name displayName Display Name
firstname First Name name.givenName First Name
lastname Last Name name.familyName Last Name
employeeIdentifier Employee ID externalId externalId
jobTitle Job Title jobTitle title
addresses.country Work Country addresses.country addresses[type eq "work"].country
addresses.locality Work City addresses.locality addresses[type eq "work"].locality
addresses.streetAddress Work Street Address addresses.streetAddress addresses[type eq "work"].streetAddress
addresses.region Work State addresses.region addresses[type eq "work"].region
addresses.postalcode Work Postal Code addresses.postalcode addresses[type eq "work"].postalCode
phoneNumbers.value Work Phone phoneNumbers.value phoneNumbers[type eq "work"].value

Importing Users

This functionality is helpful if users have already been created in the application but have not been created in JumpCloud.

  1. Log in to the JumpCloud Admin Portal.
  2. Go to USER AUTHENTICATION > SSO Applications.
  3. Search for the application and click to open its configuration panel. 
  4. Select the Identity Management tab.
  5. Click manual import.
  6. Select the users you want to create in JumpCloud from the application from the list of users that appear. Users in the list have two import statuses:
    • New – user has not been imported.
    • Imported – user has been imported and has an account in JumpCloud.

Tip: Try using the New Users-only filter when selecting users to import. This will move all of your new users to the top of the list, making them easier to identify and select.

  1. Click import.
    • If you are importing less than 100 users, your import results will display in real time and you can continue onboarding your users. 
    • If you have more than 100 users being imported, JumpCloud will send you an email when your import is complete.
  1. You can now connect and grant users access to all their JumpCloud resources. Learn more in the Authorize Users to an Application and Connecting Users to Resources articles.

Warning: Imported users must be members of a user group bound to an application for JumpCloud to manage their identity in, and access to, the application.

SCIM Directory Insights Events

The following Directory Insights (DI) events provide visibility into failures and detailed information about the user and group data being added or updated from HR or other external solutions to JumpCloud.

Note:

Customers with no package or the SSO Package will need to add the Directory Insights à la carte option. Directory Insights is included in all other packages.

SCIM DI Integration Events

Event Name Event Description
idm_integration_activate Logged when an IT admin attempts to activated new SCIM Identity Management integration.
idm_integration_update Logged when an IT admin attempts to update a configured and activated SCIM Identity Management integration.
idm_integration_reauth Logged when an IT admin attempts to change the credentials for an activated SCIM Identity Management integration.
idm_integration_delete Logged when an IT admin attempts to deactivate an activated SCIM Identity Management integration.

SCIM DI User Events

Event Name Event Description
user_create_provision Logged when JumpCloud tries to create a new user in service provider application.
user_update_provision Logged when JumpCloud tries to update an existing user in service provider application.
user_deprovision Logged when JumpCloud tries to change an existing user to inactive in the service provider application.
user_delete_provision Logged when JumpCloud tries to delete an existing user in service provider application.
user_lookup_provision Logged when JumpCloud encounters an issue when trying to lookup a user to determine if the user needs to be created or updated.

SCIM DI Group Events

Event Name Event Description
group_create_provision Logged when JumpCloud tries to create a new group in service provider application.
group_update_provision Logged when JumpCloud tries to update an existing group in service provider application.
group_delete_provision Logged when JumpCloud tries to delete an existing group in service provider application.

Removing the Integration

Important:

These are steps for removing the integration in JumpCloud. Consult your SP's documentation for any additional steps needed to remove the integration in the SP. Failure to remove the integration successfully for both the SP and JumpCloud may result in users losing access to the application.

To deactivate the IdM Integration

  1. Log in to the JumpCloud Admin Portal.
  2. Go to USER AUTHENTICATION > SSO Applications.
  3. Search for the application that you’d like to deactivate and click to open its details panel. 
  4. Under the company name and logo on the left hand panel, click the Deactivate IdM connection link.
  5. Click confirm
  6. If successful, you will receive a confirmation message.

To deactivate the SSO Integration

  1. Log in to the JumpCloud Admin Portal.
  2. Go to USER AUTHENTICATION > SSO Applications.
  3. Search for the application that you’d like to deactivate and click to open its details panel. 
  4. Select the SSO tab.
  5. Scroll to the bottom of the configuration.
  6. Click Deactivate SSO or Deactivate Bookmark
  7. Click save
  8. If successful, you will receive a confirmation message.

To delete the application

  1. Log in to the JumpCloud Admin Portal.
  2. Go to USER AUTHENTICATION > SSO Applications.
  3. Search for the application that you’d like to delete.
  4. Check the box next to the application to select it.
  5. Click Delete.
  6. Enter the number of the applications you are deleting
  7. Click Delete Application.
  8. If successful, you will see an application deletion confirmation notification.

List IconIn this Article

Still Have Questions?

If you cannot find an answer to your question in our FAQ, you can always contact us.

Submit a Case