Set up a FIS IBS connector

Capabilities

The FIS IBS connector syncs the following resources:

Resource	Sync	Provision
Users
Roles

Provisioning operations supported:

Grant or revoke role membership
Create and delete user accounts
Update user profile (first name, last name, email)
Enable or disable user accounts

Gather FIS IBS credentials

To configure the FIS IBS connector, you need administrator access to the FIS Code Connect developer portal and your institution’s FIS IBS identifiers (FiId, sourceId, appId, prcsGrpId).

Create a new application and subscribe it to the IBS Entitlement API:

Navigate to My Apps and click Create Application.
Name the application (for example, ConductorOne).
Subscribe the application to the IBS Entitlement API.
Copy the Consumer Key (client ID) and Consumer Secret (client secret) shown on the application page.

Obtain your institution’s FIS IBS identifiers from your FIS account representative or system administrator:

FiId — the financial institution organization ID (for example, BADEFAULT-241)
sourceId — the IBS data source identifier (for example, E1ANY0)
appId — the IBS application identifier (for example, ET)
prcsGrpId — the processing group ID to scope roles (for example, 547)

Note the API base URL for your environment. For FIS Code Connect (cloud gateway) it follows the pattern https://api-gw-<env>.fisglobal.com/rest/IBSET/v4. For a direct VPN connection, use the internal FIS host URL provided by your FIS representative.

Configure the FIS IBS connector

Cloud-hosted
Self-hosted

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

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

Search for FIS IBS and click Add.

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.

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

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

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

Find the Settings area of the page and click Edit.

Enter the required configuration:

FIS IBS Base URL: The Entitlement API base URL (for example, https://api-gw-uat.fisglobal.com/rest/IBSET/v4)
OAuth Client ID: The Consumer Key from the FIS Code Connect portal
OAuth Client Secret: The Consumer Secret from the FIS Code Connect portal
Organization ID (FiId): Your financial institution identifier (for example, BADEFAULT-241)
Source ID: Your IBS source identifier (for example, E1ANY0)
Application ID: Your IBS application identifier (for example, ET)
Processing Group ID: The processing group to scope roles (for example, 547)

Click Save.

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

Done. Your FIS IBS connector is now pulling access data into C1.

Follow these instructions to use the FIS IBS 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.

Step 1: Set up a new FIS IBS connector

In C1, navigate to Apps > Connectors > Add connector.

Search for Baton and click Add.

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

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

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

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.

Step 2: Create Kubernetes configuration files

Create two Kubernetes manifest files for your FIS IBS connector deployment:

Secrets configuration

# baton-fis-ibs-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-fis-ibs-secrets
type: Opaque
stringData:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 client secret>

  # FIS IBS credentials
  BATON_FIS_IBS_BASE_URL: https://api-gw-<env>.fisglobal.com/rest/IBSET/v4
  BATON_FIS_IBS_CLIENT_ID: <FIS Code Connect Consumer Key>
  BATON_FIS_IBS_CLIENT_SECRET: <FIS Code Connect Consumer Secret>
  BATON_FIS_IBS_ORG_ID: <FiId, e.g. BADEFAULT-241>
  BATON_FIS_IBS_SOURCE_ID: <sourceId, e.g. E1ANY0>
  BATON_FIS_IBS_APP_ID: <appId, e.g. ET>
  BATON_FIS_IBS_PRCS_GRP_ID: <prcsGrpId, e.g. 547>

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

Deployment configuration

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

Step 3: Deploy the connector

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

Check that the connector data uploaded correctly. In C1, click Applications. On the Managed apps tab, locate and click the name of the application you added the FIS IBS connector to. FIS IBS data should be found on the Entitlements and Accounts tabs.

Done. Your FIS IBS connector is now pulling access data into C1.

Notes

FIS Code Connect vs. direct VPN The connector works with both connection methods. Responses from the FIS Code Connect cloud gateway are double-encoded JSON; the connector detects and unwraps this automatically. No configuration change is required. Multiple processing groups The connector is scoped to a single processing group (prcsGrpId). If your institution has roles or users spread across multiple processing groups, run one connector instance per group.

All versions of this connector are available at dist.conductorone.com.

Welcome

Manage connectors

Deploy connectors

Upload connector data

Configurable connectors

Pre-built connectors

Set up a FIS IBS connector

Capabilities

Gather FIS IBS credentials

Configure the FIS IBS connector

Step 1: Set up a new FIS IBS connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector

Notes

​Capabilities

​Gather FIS IBS credentials

​Configure the FIS IBS connector

​Step 1: Set up a new FIS IBS connector

​Step 2: Create Kubernetes configuration files

​Secrets configuration

​Deployment configuration

​Step 3: Deploy the connector

​Notes

Capabilities

Gather FIS IBS credentials

Configure the FIS IBS connector

Step 1: Set up a new FIS IBS connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector

Notes