ConductorOne docs

Set up a RingCentral connector

ConductorOne provides identity governance and just-in-time provisioning for RingCentral. Integrate your RingCentral instance with ConductorOne to run user access reviews (UARs) and enable just-in-time access requests.

Capabilities

Resource	Sync	Provision
Accounts	✅
Roles	✅	✅

Gather RingCentral credentials

Each setup method requires you to pass in credentials generated in RingCentral. Gather these credentials before you move on.

A user with access to the RingCentral Developer Console must perform this task.

Create a JWT application

Log into the RingCentral Developer Console.
Navigate to Console > Apps and click Create App.
In the What type of app are you creating? area, select REST API App, then click Next.
In the Authentication area, select JWT auth flow.
In the Security area, add the following permissions:
- Read Accounts
- Edit Extensions
- Role Management
Select This app is private and will only be callable using credentials from the same RingCentral account.
The new app is created. Carefully copy and save the client ID and client secret.

Create a JWT token

In the upper right corner of the screen, click your name and select Credentials.
Click Create JWT.
Give the JWT a name, such as “ConductorOne” and select the environment where it will be used.
Select the Only specific apps of my choice option and enter the client ID of your newly created app.
Click Create. Carefully copy and save the JWT token.

That’s it! Next, move on to the connector configuration instructions.

Configure the RingCentral connector

To complete this task, you’ll need:
The Connector Administrator or Super Administrator role in ConductorOne
Access to the set of RingCentral credentials generated by following the instructions above

Follow these instructions to use a built-in, no-code connector hosted by ConductorOne.

In ConductorOne, navigate to Admin > Connectors and click Add connector.
Search for RingCentral and click Add.

Don’t see the RingCentral connector? Reach out to support@conductorone.com to add RingCentral to your Connectors page.

Choose how to set up the new RingCentral connector:
- Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with ConductorOne)
- Add the connector to a managed app (select from the list of existing managed apps)
- Create a new managed app
Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed.
If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process.
Click Next.
Find the Settings area of the page and click Edit.
Enter the client ID and secret in the Client ID and Client Secret fields.
Enter the JWT token in the JWT field.
Click Save.
The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.

That’s it! Your RingCentral connector is now pulling access data into ConductorOne.

Follow these instructions to use the RingCentral connector, hosted and run in your own environment.

When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with ConductorOne, automatically syncing and uploading data at regular intervals. This data is immediately available in the ConductorOne UI for access reviews and access requests.

Step 1: Configure the RingCentral connector

In ConductorOne, navigate to Connectors > Add connector.
Search for Baton and click Add.
Choose how to set up the new RingCentral connector:
- Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with ConductorOne)
- Add the connector to a managed app (select from the list of existing managed apps)
- Create a new managed app
Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed.
If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process.
Click Next.
In the Settings area of the page, click Edit.
Click Rotate to generate a new Client ID and Secret.
Carefully copy and save these credentials. We’ll use them in Step 2.

Step 2: Create Kubernetes configuration files

Create two Kubernetes manifest files for your RingCentral connector deployment:

Secrets configuration

# baton-ringcentral-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-ringcentral-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>
  
  # RingCentral credentials
  BATON_RINGCENTRAL_CLIENT_ID: <RingCentral client ID>
  BATON_RINGCENTRAL_CLIENT_SECRET: <RingCentral client secret>
  BATON_RINGCENTRAL_JWT: <RingCentral JWT token>

See the connector’s README or run --help to see all available configuration flags and environment variables.

Deployment configuration

# baton-ringcentral.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-ringcentral
  labels:
    app: baton-ringcentral
spec:
  selector:
    matchLabels:
      app: baton-ringcentral
  template:
    metadata:
      labels:
        app: baton-ringcentral
        baton: true
        baton-app: ringcentral
    spec:
      containers:
      - name: baton-ringcentral
        image: ghcr.io/conductorone/baton-ringcentral:latest
        imagePullPolicy: IfNotPresent
        envFrom:
        - secretRef:
            name: baton-ringcentral-secrets

Step 3: Deploy the connector

Create a namespace in which to run ConductorOne connectors (if desired), then apply the secret config and deployment config files.
Check that the connector data uploaded correctly. In ConductorOne, click Applications. On the Managed apps tab, locate and click the name of the application you added the RingCentral connector to. RingCentral data should be found on the Entitlements and Accounts tabs.

That’s it! Your RingCentral connector is now pulling access data into ConductorOne.