Set up an Oracle Field Service connector

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

Capabilities

Resource	Sync	Provision
Accounts
Collaboration groups
Resources
Roles

The Oracle Field Service connector supports automatic account provisioning and deprovisioning.

When a new account is created by C1, the account’s password will be sent to a vault.

Entitlement provisioning

The connector provisions the following entitlements:

• Role (user type): granting a role to a user sets the user’s userType via PATCH /rest/ofscCore/v1/users/{login}. Because userType is single-valued and required in Oracle Field Service, the role entitlement does not support revoke. To change a user’s role, grant a different role; the new value replaces the previous one.
• Resource: granting a Field Service resource to a user adds the resource ID to the user’s resources array via PATCH /rest/ofscCore/v1/users/{login}. Revoke removes it. Oracle Field Service replaces the array on PATCH, so the connector reads the current array, mutates it, and writes the full list back.

Gather Oracle Field Service credentials

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

A user with the Administrator role in Oracle Field Service must perform this task.

Register a client application

1. In the OFS Manage interface, navigate to Configuration > Applications.

2. In the left pane, click the + icon to add a new application.

3. In the New application window, provide the following details:

   • Application Name: A descriptive name you can easily recognize (for example, “C1 Connector”).
   • Application ID: A unique identifier (for example, “c1-connector”).
4. Click Save. The application is created.

Configure authentication and get credentials

1. From the application list on the left, select the application you just created.

2. In the General info tab, ensure the Active checkbox is selected.

3. From the Token service dropdown menu, select OFS.

4. Under the Authentication settings section, check the box for Authenticate using Client ID/Client Secret.

5. Click the Show Client ID/Client Secret button. Carefully copy and save the client ID and client secret.

6. Click Save to apply the settings.

Enable API access and permissions

1. In the same application configuration screen, find the API access section and click Add new.

2. A window will appear with a list of available APIs. Select the following API:

   • Core API
3. After adding this API, you must grant specific permissions for it. Navigate to the API’s Available entities and select the following entities:

   • Core API
     • User entity: Read/write (or Read if you do not want C1 to provision access)
     • Resource entity: Read
4. Review the Additional Restrictions section below the API list.

   Do not check “Allow access only to certain resources” or “Allow access only for certain IP-addresses” unless you have a specific security requirement to do so, as it may interfere with the connector’s operation.

5. Once you have set the permissions for both APIs, click Save on the main application screen to finalize the configuration.

Done. Next, move on to the connector configuration instructions.

Configure the Oracle Field Service connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in C1
• Access to the set of Oracle Field Service credentials generated by following the instructions above

Cloud-hosted

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

1. In C1, navigate to Apps > Connectors and click Add connector.

2. Search for Oracle Field Service and click Add.

3. Choose where to add the connector: Create a new app, or Add to an existing app (then select the app).

   If you’re creating a new app, choose whether to link it to an application discovered from your identity provider: select Yes and pick the IdP application, or No to continue with just the connector.

4. Set the connector’s Name and, optionally, a Description.

5. Click the pencil icon next to Owners to choose who can configure and manage this connector.

6. Click Add. The connector is created and its configuration page opens.

7. Find the Settings area of the page and click Edit.

8. If your Oracle Field Service tenant uses full emails as login names, click to enable the Login has email option. Leave this option unchecked if your tenant uses usernames without email domains.

9. Paste the client ID and client secret into the relevant fields.

10. Enter your Oracle Field Service instance domain in the Instance URL field.

11. Click Save.

12. The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.

Done. Your Oracle Field Service connector is now pulling access data into C1.

Self-hosted

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

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

Resources

• Official download center: For stable binaries (Windows/Linux/macOS) and container images.

Step 1: Set up a new Oracle Field Service connector

1. In C1, navigate to Apps > Connectors and click Add connector.

2. Search for Baton and click Add.

3. Choose where to add the connector: Create a new app, or Add to an existing app (then select the app).

   If you’re creating a new app, choose whether to link it to an application discovered from your identity provider: select Yes and pick the IdP application, or No to continue with just the connector.

4. Set the connector’s Name and, optionally, a Description.

5. Click the pencil icon next to Owners to choose who can configure and manage this connector.

6. Click Add. The connector is created and its configuration page opens.

7. In the Settings area of the page, click Edit.

8. 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 Field Service connector deployment:

Secrets configuration

# baton-oracle-field-service-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-oracle-field-service-secrets
type: Opaque
stringData:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 client secret>
  
  # Oracle Field Service credentials
  BATON_OFS_CLIENT_ID: <Oracle Field Service client ID>
  BATON_OFS_CLIENT_SECRET: <Oracle Field Service client secret>
  BATON_OFS_INSTANCE_URL: <Oracle Field Service tenant URL, in the form "https://instance.fs.ocs.oraclecloud.com">

  #Optional: Include if you want to use login as email. If set to false (default), emails will be fetched  from Resources (this is a slower option).
  BATON_LOGIN_HAS_EMAIL: true

  # Optional: Include if you want C1 to provision access using this connector
  BATON_PROVISIONING: true

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

Deployment configuration

# baton-oracle-field-service.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-oracle-field-service
  labels:
    app: baton-oracle-field-service
spec:
  selector:
    matchLabels:
      app: baton-oracle-field-service
  template:
    metadata:
      labels:
        app: baton-oracle-field-service
        baton: true
        baton-app: oracle-field-service
    spec:
      containers:
      - name: baton-oracle-field-service
        image: public.ecr.aws/conductorone/baton-oracle-field-service:latest
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-oracle-field-service
        envFrom:
        - secretRef:
            name: baton-oracle-field-service-secrets

Step 3: Deploy the connector

1. Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files.

2. Check that the connector data uploaded correctly. In C1, click Apps. On the Managed apps tab, locate and click the name of the application you added the Oracle Field Service connector to. Oracle Field Service data should be found on the Entitlements and Accounts tabs.

Done. Your Oracle Field Service connector is now pulling access data into C1.