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 and groups in RingCentral from JumpCloud using the Identity Management (SCIM) integration. Leverage this integration to centralize user lifecycle, user identity, and group management in JumpCloud for RingCentral. Save time and avoid mistakes, as well as potential security risks, related to manually creating users.
Read this article to learn how to configure the RingCentral integration.
Prerequisites:
- A JumpCloud administrator account.
- JumpCloud SSO Package or higher or SSO à la carte option.
- A RingCentral administrator account with a Premium or Enterprise plan.
- Your RingCentral domain.
Important Considerations
- We recommend that you activate SSO for RingCentral prior to creating an Identity Management integration with RingCentral to simplify the login process for your users and reduce the number of usernames and passwords they have to remember. If you aren’t going to use SSO, we recommend that you hide it to prevent it from appearing in the User Portal Application list.
- RingCentral supports a number user attribute that is populated by default and required for SSO to work. Optionally, you can map a JumpCloud user attribute to this field to dynamically apply a user’s number to their account. Alternately, you can use JumpCloud custom attributes to store and pass this value in an assertion.
- The administrator's email address must be URL encoded, e.g., for an email address of [email protected], the encoded email address is testing12%2B3%2540jumpcloud.com. To encode your email address:
- Navigate to your URL Encoder of choice or use this URL Encoding tool.
- Type your email address (which should be used by both your JumpCloud account and your RingCentral administrator account) into the blue field.
- Select Encode.
- Copy the generated value for use while configuring JumpCloud.
- The RingCentral API is based on version 2.0 of the SCIM standard and runs under the RingCentral REST API.
- Learn more about RingCentral SCIM implementation at API Reference: Provisioning.
- The RingCentral account must have available DigitalLines (licenses) to provision users from JumpCloud.
- RingCentral SCIM integration requires a User Admin or higher role. Learn more about RingCentral’s User Roles and Permissions.
- If you delete an integrated RingCentral application from your Applications list, the application is removed from JumpCloud, but any previously bound users remain active in RingCentral. These users will be able log in to RingCentral with the password they used prior to enablement of SSO to the RingCentral application from your JumpCloud account.
- If you deactivate the Identity Management on your RingCentral application and SSO is activated, previously bound users remain active in RingCentral and are able to authenticate using SSO. No further updates will be made to user accounts via the Identity Management integration.
- Users created via SCIM integration should also be deleted via SCIM integration. Otherwise, the administrator must disable the user prior to deleting them.
- Users deactivated via the SCIM integration can only be deleted via the SCIM integration after reactivating them and then deleting them.
- If you need to update your token, you must deactivate the IdM integration, update the token, and then reactivate the IdM integration.
- Newly provisioned users receive an activation email with a link to set up their account.
- User accounts in a pending status can’t be managed; they can only be deleted.
- If a user’s password expires in JumpCloud, their account becomes suspended and they are deactivated in all applications that have Identity Management configured and, are associated to them. Once the user’s password is updated, the account and previously associated applications are reactivated.
Attribute Considerations
- A default set of attributes are managed for users. See the Attribute Mappings section for more details.
- Any extra attributes sent to the API are ignored. If you define an address for a user, you must set a country value. The country value must match one of the countries associated with an unassigned extension, otherwise, the user isn't added to RingCentral.
- At the moment of provisioning the username and email should match.
Creating a new JumpCloud Application Integration
- Log in to the JumpCloud Admin Portal.
- Go to USER AUTHENTICATION > SSO Applications.
- Click + Add New Application.
- Type the name of the application in the Search field and select it.
- Click Next.
- Optionally, customize the display label, description and how the application displays:
- Description - add a description that users will see in their user portal
- User Portal Image - choose Logo or Color Indicator
- Show in User Portal - enable this option for this to be visible in the user portal
- Optionally, customize the IdP URL:
- Expand Advanced Settings and enter the name you want to use for the end of the SSO IdP URL, https://sso.jumpcloud.com/saml2/{custom_value}
The SSO IdP URL is not editable after the application is created. You will have to delete and recreate the connector if you need to edit this field at a later time.
- Click Save Application.
- 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.
- Select the SSO tab.
- Replace any instances of <mydomain> with your RingCentral domain name.
- Add or change any attributes.
- Click save.
Copy the metadata URL
- Find your application in the Configured Applications list and click anywhere in the row to reopen its configuration window.
- Select the SSO tab and click Copy Metadata URL.
- The URL will be copied to your clipboard.
To configure RingCentral 1
- Login to RingCentral as as administrator.
- Go to: More > Security and Compliance > Single Sign-on.
- In the Set up SSO by yourself section, click Edit
- In the Upload IDP Metadata section:
- Select URL from the dropdown menu.
- Enter the JumpCloud Metadata URL.
- Click Import.
- In the Attribute Mapping section, select Custom from the Map Email Attribute to dropdown menu, then enter email in the field that appears.
- Click Save.
- In the Set up SSO by yourself section, click Download to obtain your SP metadata.
To configure JumpCloud 2
- Find RingCentral in the list of configured applications and click Configure.
- Select the SSO tab.
- Upload the RingCentral metadata file by clicking Upload Metadata.
- Click save.
To configure RingCentral 2
- Navigate to Tools > Single Sign-on.
- Select the Enable SSO option under Enable SSO.
- In Manage Your Login, configure SSO/password settings.
- Click Save.
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 Applications, Users List or User Groups page.
To authorize user access from the Application’s page
- Log in to the JumpCloud Admin Portal.
- Go to USER AUTHENTICATION > SSO Applications, then select the application to which you want to authorize user access.
- Select the User Groups tab. If you need to create a new group of users, see Get Started: User Groups.
- Select the check box next to the desired group of users to which you want to give access.
- Click Save.
To learn how to authorize user access from the Users or User Groups pages, see Authorize Users to an SSO Application.
Validate SSO authentication workflows
At this time, single sign on with RingCentral works only as an SP initiated request.
SP Initiated Authentication Workflows
- 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
- Create a new application or select it from the Configured Applications list.
- Select the Identity Management tab.
- Click configure.
- You’re prompted to sign in to your RingCentral account.
- You’re prompted to give JumpCloud permission to administer your organization's RingCentral workspace.
- Click Authorize.
- If you aren’t a RingCentral User Admin role or higher, you see a request asking for administrator permissions. You’re required to have a RingCentral User Admin role account to complete the integration with JumpCloud.
- You receive a confirmation that the Identity Management integration has been successfully verified.
Attribute Mappings
The Export Attributes Mapping table lists the Required and Optional Mappings that JumpCloud sends to the Service Provider. See Attribute Considerations for more information regarding attribute mapping considerations.
Learn about JumpCloud Properties and how they work with system users in our API.
Modifying User Attributes
It's highly recommended you use all optional mappings. This creates a more complete user profile, enabling better automation and more accurate access management within the application.
To add user attributes
- From your connector’s configuration page, select the Identity Management tab.
- Expand the Export Attribute Mapping section and click Edit. The Optional Mappings table will open.
- Scroll to the bottom of the table and click +Add Attribute.
- Select one of the mapping types:
- Direct Mapping (JSON Path) - send the value from a user attribute in JumpCloud directly to an attribute in the service provider
- From the JumpCloud Attribute dropdown, select the desired attribute
- If you choose “Custom User Attribute” you must type the name of the attribute exactly as it on the user details page. To see the dropdown again, you must delete the attribute and add a new attribute
- From the SCIM Attribute dropdown, select the corresponding (destination) attribute
- From the JumpCloud Attribute dropdown, select the desired attribute
- Expression - transform or combine multiple user attributes into a single, custom value before sending it to the service provider
- Enter the expression in the JumpCloud Attribute field
- From the SCIM Attribute dropdown, select the corresponding (destination) attribute
- Constant - send a fixed, predefined value—like a specific company name —for every user to the service provider
- This is a free text field with no validation, e.g., the attribute must match exactly, including case, to the corresponding attribute in the user record. Once the custom attribute is added, you must delete it and readd a new custom attribute to see the dropdown again.
- Direct Mapping (JSON Path) - send the value from a user attribute in JumpCloud directly to an attribute in the service provider
- Repeat these steps for additional attributes.
- Click Preview Mappings to review the User Schema.
- If you do not select a specific user from the Preview Filter dropdown, the schema will default to the first user.
- Click Update.
Updates to the user schema will not dynamically sync. To force a sync, you must modify the user group’s record in some way, like adding a space to the Description field.
To modify existing user attributes
This new functionality is in Private Preview. Contact your Account Manager to enable it. Your feedback helps us evolve this feature so share your suggestions at the bottom of the article. Learn More
This enhancement gives you complete control over the user attributes sent from JumpCloud to this application. You can now:
- Fully control mappings - define which JumpCloud attribute or source data corresponds to an attribute in the SP's SCIM schema
- Use a variety of source values - map data from the user's standard attributes, Manager field, custom attributes, or other data sources
- Manipulate data with expressions - transform data, such as preferred first names and date format, using expressions before transmission to the SP. Learn more
- Preview changes - review your new mappings to ensure accuracy before you save
- From your connector’s configuration page, select the Identity Management tab.
- Expand the Export Attribute Mapping section and click Edit.
- For the type of attribute you would like to modify:
- Direct - select the new attribute from the dropdown(s)
- Expression - click in the Expression field and make the desired edits. If necessary, select the new attribute from the SCIM Attribute dropdown
- Custom - delete the existing values in either or both of the attribute fields and enter the new values
- Click Preview Mappings to review the updated User Schema.
- Click Update.
Updates to the user schema will not dynamically sync. To force a sync, you must modify the user group’s record in some way, like adding a space to the Description field.
To delete user attributes
- From your connector’s configuration page, select the Identity Management tab.
- In the Export Attribute Mapping section, click Edit. The Optional Mappings table will open.
- Click Delete (
) to remove any optional attributes.
- When finished, click Update.
Attributes that were initially included and populated in the user record and then deleted at a later time will not be modified or removed from the user record.
To restore the default Optional Mappings, click Edit > Restore Defaults > Update.
RingCentral User Attributes
JumpCloud Property | JumpCloud UI | SCIM v2 Mapping | RingCentral Value |
---|---|---|---|
Company Email | emails: value | ||
username | Username | userName | userName |
firstname | First Name | name.givenName | name.givenName |
lastname | Last Name | name.familyName | name.familyName |
addresses[].type | addresses[].type | addresses[].type | addresses[].type |
addresses[].streetAddress | addresses[].streetAddress | addresses[].streetAddress | addresses[].streetAddress |
addresses[].locality | addresses[].locality | addresses[].locality | addresses[].locality |
addresses[].region | addresses[].region | addresses[].region | addresses[].region |
addresses[].postalCode | addresses[].postalCode | addresses[].postalCode | addresses[].postalCode |
addresses[].country | addresses[].country | addresses[].country | addresses[].country |
phoneNumbers[].type | phoneNumbers[].type | phoneNumbers[].type | phoneNumbers[].type |
phoneNumbers[].value | phoneNumbers[].value | phoneNumbers[].value | phoneNumbers[].value |
department | Department | urn:scim:schemas:extension:enterprise:2.0 | urn:scim:schemas:extension:enterprise:2.0 |
Importing Users
This functionality is helpful if users have already been created in the application but have not been created in JumpCloud.
Users that are suspended in the application will not be created in JumpCloud.
- Log in to the JumpCloud Admin Portal.
- Go to USER AUTHENTICATION > SSO Applications.
- Search for the application and click to open its configuration panel.
- Select the Identity Management tab.
- Click Manual Import.
- 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.
- 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
- 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.
Customers with no package or the Device Management 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
These DI events will only be present if SCIM Groups are supported.
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
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
- Log in to the JumpCloud Admin Portal.
- Go to USER AUTHENTICATION > SSO Applications.
- Search for the application that you’d like to deactivate and click to open its details panel.
- Under the company name and logo on the left hand panel, click the Deactivate IdM connection link.
- Click confirm.
- If successful, you will receive a confirmation message.
To deactivate the SSO Integration or Bookmark
- Log in to the JumpCloud Admin Portal.
- Go to USER AUTHENTICATION > SSO Applications.
- Search for the application that you’d like to deactivate and click to open its details panel.
- Select the SSO or Bookmark tab.
- Scroll to the bottom of the configuration.
- Click Deactivate SSO or Deactivate Bookmark.
- Click save.
- If successful, you will receive a confirmation message.
To delete the application
- Log in to the JumpCloud Admin Portal.
- Go to USER AUTHENTICATION > SSO Applications.
- Search for the application that you’d like to delete.
- Check the box next to the application to select it.
- Click Delete.
- Enter the number of the applications you are deleting
- Click Delete Application.
- If successful, you will see an application deletion confirmation notification.