Enable RingCentral bidirectional attribute synchronization

Typically, Okta or Active Directory (AD) are the sources of truth for user profile attributes. When you integrate RingCentral with Okta, the Direct Number and Extension attributes must come from RingCentral. Enabling bidirectional synchronization for these attributes allows RingCentral attribute data to be shared with Okta or AD.

  1. Contact Okta support and ask to have profile sourcing and push functionality enabled.
  2. In the Admin Console, go to DirectoryProfile Editor.
  3. In the Search field, enter RingCentral.
  4. Click Profile for the RingCentral User instance you want to edit.
  5. Click Add Attribute, select Direct Number and Extension Number, and click Save.
  6. Click Mappings and select the RingCentral to Okta User tab.
  7. Map a user's phone number to the primaryPhone attribute and click Save Mappings. For example, entering (appuser.directNumber != null ? appuser.directNumber : "") + "#" + appuser.extensionNumber maps the user's primary phone number and extension to the primaryPhone attribute.
  8. Set RingCentral as the profile source for the primaryPhone attribute:
  1. Click Applications and enter RingCentral in the Search field.
  2. Click the RingCentral link for the RingCentral app you want to edit.
  3. Click the Provisioning tab and select To Okta in the SETTINGS list.
  4. Scroll down and in the Okta Attributes Mappings area, click Go to Profile Editor.
  5. Click the Information () icon for the primaryPhone attribute.
  6. In the Source priority list, select Override profile source and select RingCentral in the Add Source list.
  7. Click Save Attribute.
  1. Optional. If you have other applications acting as profile sources, confirm the RingCentral source priority is set correctly:
    1. Go to DirectoryProfile Sources.
    2. Move RingCentral up or down in priority.