Use ºÚÁϺ£½Ç91Èë¿Ú 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 ºÚÁϺ£½Ç91Èë¿Ú using the Identity Management (SCIM) integration. Leverage this integration to centralize user lifecycle, user identity, and group management in ºÚÁϺ£½Ç91Èë¿Ú 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 ºÚÁϺ£½Ç91Èë¿Ú administrator account.
- ºÚÁϺ£½Ç91Èë¿Ú 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 ºÚÁϺ£½Ç91Èë¿Ú user attribute to this field to dynamically apply a user’s number to their account. Alternately, you can use ºÚÁϺ£½Ç91Èë¿Ú 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 .
- Type your email address (which should be used by both your ºÚÁϺ£½Ç91Èë¿Ú account and your RingCentral administrator account) into the blue field.
- Select Encode.
- Copy the generated value for use while configuring ºÚÁϺ£½Ç91Èë¿Ú.
- 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 .
- The RingCentral account must have available DigitalLines (licenses) to provision users from ºÚÁϺ£½Ç91Èë¿Ú.
- RingCentral SCIM integration requires a User Admin or higher role. Learn more about .
- If you delete an integrated RingCentral application from your Applications list, the application is removed from ºÚÁϺ£½Ç91Èë¿Ú, 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 ºÚÁϺ£½Ç91Èë¿Ú 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 ºÚÁϺ£½Ç91Èë¿Ú, 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 ³Ü²õ±ð°ù²Ô²¹³¾±ðÌý²¹²Ô»åÌý±ð³¾²¹¾±±ôÌýshould match.
Creating a new ºÚÁϺ£½Ç91Èë¿Ú Application Integration
- Log in to the .
- 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.
- 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.
If this is a Bookmark Application, enter your sign-in URL in the Bookmark URL field.
- Optionally, expand Advanced Settings to specify a value for the SSO IdP URL. If no value is entered, it will default to https://sso.jumpcloud.com/saml2/<applicationname>.
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 ºÚÁϺ£½Ç91Èë¿Ú 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 ºÚÁϺ£½Ç91Èë¿Ú 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 ºÚÁϺ£½Ç91Èë¿Ú 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 ºÚÁϺ£½Ç91Èë¿Ú, 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
- Log in to the .
- 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 group of users you want to give access.
- Click save.
To learn how to authorize user access from the Groups Configuration panel, 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 ºÚÁϺ£½Ç91Èë¿Ú 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 ºÚÁϺ£½Ç91Èë¿Ú 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 ºÚÁϺ£½Ç91Èë¿Ú.
- You receive a confirmation that the Identity Management integration has been successfully verified.
Attribute Mappings
The following table lists attributes that ºÚÁϺ£½Ç91Èë¿Ú sends to the application. See Attribute Considerations for more information regarding attribute mapping considerations.
Learn about ºÚÁϺ£½Ç91Èë¿Ú Properties and how they work with system users in our .
RingCentral User Attributes
ºÚÁϺ£½Ç91Èë¿Ú Property | ºÚÁϺ£½Ç91Èë¿Ú 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 ºÚÁϺ£½Ç91Èë¿Ú.
- Log in to the .
- 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 ºÚÁϺ£½Ç91Èë¿Ú from the application from the list of users that appear. Users in the list have two import statuses:
- ±·±ð·ÉÌý- user has not been imported
- ±õ³¾±è´Ç°ù³Ù±ð»åÌý- user has been imported and has an account in ºÚÁϺ£½Ç91Èë¿Ú
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, ºÚÁϺ£½Ç91Èë¿Ú will send you an email when your import is complete
- You can now connect and grant users access to all their ºÚÁϺ£½Ç91Èë¿Ú 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 ºÚÁϺ£½Ç91Èë¿Ú 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 ºÚÁϺ£½Ç91Èë¿Ú.
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 .
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 ºÚÁϺ£½Ç91Èë¿Ú tries to create a new user in service provider application. |
user_update_provision | Logged when ºÚÁϺ£½Ç91Èë¿Ú tries to update an existing user in service provider application. |
user_deprovision | Logged when ºÚÁϺ£½Ç91Èë¿Ú tries to change an existing user to inactive in the service provider application. |
user_delete_provision | Logged when ºÚÁϺ£½Ç91Èë¿Ú tries to delete an existing user in service provider application. |
user_lookup_provision | Logged when ºÚÁϺ£½Ç91Èë¿Ú 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 ºÚÁϺ£½Ç91Èë¿Ú tries to create a new group in service provider application. |
group_update_provision | Logged when ºÚÁϺ£½Ç91Èë¿Ú tries to update an existing group in service provider application. |
group_delete_provision | Logged when ºÚÁϺ£½Ç91Èë¿Ú tries to delete an existing group in service provider application. |
Removing the Integration
These are steps for removing the integration in ºÚÁϺ£½Ç91Èë¿Ú. 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 ºÚÁϺ£½Ç91Èë¿Ú may result in users losing access to the application.
To deactivate the IdM Integration
- Log in to the .
- 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 .
- 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 .
- 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.