Set up an Oracle IDCS connector

ConductorOne provides identity governance for Oracle Identity Cloud Service (IDCS). Integrate your Oracle IDCS instance with ConductorOne to run user access reviews (UARs) and enable just-in-time access requests.

Capabilities

Resource	Sync	Provision
Accounts	✅	✅
Groups	✅	✅
Applications	✅*	✅**
Application roles	✅*	✅**

The Oracle IDCS connector supports automatic account provisioning and deprovisioning.

*You can opt into syncing application and application role data; these are not synced by default.

**Application access and application roles that are inherited via group membership cannot be deprovisioned using ConductorOne.

Performance considerations

API Latency for Grant Operations: The Oracle IDCS API has inherent latency when creating grants (assigning access to applications or application roles). Due to this latency, we recommend avoiding performing rapid grant and revoke operations in quick succession, as this may result in failures or inconsistent states. Allow sufficient time between operations to ensure the API has completed processing the previous request before initiating the next one.
Rate Limiting: The connector implements rate limiting to respect Oracle IDCS API limits. If you encounter rate limiting errors, the connector will automatically retry with appropriate backoff strategies.

Gather Oracle IDCS credentials

Configuring the connector requires you to pass in credentials generated in Oracle IDCS. Gather these credentials before you move on.

A user with the Identity Domain Administrator or Application Administrator in Oracle IDCS must perform this task.

Create a confidential application

In the Oracle Cloud Infrastructure console, navigate to Identity & Security > Identity and click Domains.
Select the appropriate domain. Your Oracle IDCS API Base Domain is the Domain URL shown on this page (for example, https://idcs-xxxxxxxx.identity.oraclecloud.com).
In the domain’s navigation menu, click Integrated applications.
Click Add application, select Confidential application, and then click Launch workflow.
Enter a name for the application, such as “ConductorOne”, then click Next.
On the OAuth Configuration page, click Edit OAuth configuration and select Configure this application as a client.
For Allowed GrantTypes, check Client Credentials.
Scroll down to the Token issuance policy section and click + Add app role.
Select a role that has permission you want to give to the integration (see below), then click Add.
To enable syncing (read-only), a role with read-only access to users and groups, like Identity Domain Auditor, is sufficient. To enable provisioning (read-write), the application needs a role with write permissions for users and groups, such as Identity Domain Administrator, which includes the Users - Manage and Groups - Manage permissions.
Click Submit.
The OAuth Configuration page will display the Client ID (api-access-id) and Client Secret (api-access-secret). Carefully copy and save these credentials.
Activate the application using the Actions button in the top right, then click Activate.

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

Configure the Oracle IDCS connector

To complete this task, you’ll need:
The Connector Administrator or Super Administrator role in ConductorOne
Access to the set of Oracle IDCS 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 Oracle IDCS and click Add.
Choose how to set up the new Oracle IDCS 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 Client secret into the Access ID and Access key fields.
Enter the your Oracle ICDS base domain into the Base domain for API field.
Optional. Click Sync apps and roles if you want to opt into syncing application and application role data.
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 Oracle IDCS connector is now pulling access data into ConductorOne.

Follow these instructions to use the Oracle IDCS 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: Set up a new Oracle IDCS connector

In ConductorOne, navigate to Connectors > Add connector.
Search for Baton and click Add.
Choose how to set up the new Oracle IDCS 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 Oracle IDCS connector deployment:

Secrets configuration

# baton-oracle-idcs-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-oracle-idcs-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>
  
  # Oracle IDCS credentials
  BATON_API_ACCESS_ID: <Oracle IDCS app client ID>
  BATON_API_ACCESS_SECRET: <Oracle IDCS app client secret>
  BATON_API_BASE_DOMAIN: <Oracle IDCS API base domain>

  # Optional: include if you want ConductorOne to provision access using this connector
  BATON_PROVISIONING: true

  # Optional: include if you want ConductorOne to sync application and application role data
  BATON_SYNC_APPS_AND_ROLES: true

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

Deployment configuration

# baton-oracle-idcs.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-oracle-idcs
  labels:
    app: baton-oracle-idcs
spec:
  selector:
    matchLabels:
      app: baton-oracle-idcs
  template:
    metadata:
      labels:
        app: baton-oracle-idcs
        baton: true
        baton-app: oracle-idcs
    spec:
      containers:
      - name: baton-oracle-idcs
        image: ghcr.io/conductorone/baton-oracle-idcs:latest
        imagePullPolicy: IfNotPresent
        envFrom:
        - secretRef:
            name: baton-oracle-idcs-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 Oracle IDCS connector to. Oracle IDCS data should be found on the Entitlements and Accounts tabs.

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