Set up an nCino connector

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

Capabilities

Resource	Sync	Provision
Accounts (Team members)	✅
Accounts (Loan officers)	✅
Loans	✅

Gather nCino credentials

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

A user with the Company Admin role in nCino must perform this task.

Generate

Make sure the nCino Mortgage API is enabled on your account.
In nCino, navigate to Company Settings > API Management.
If relevant, select nCino Mortgage from the dropdown of APIs.
On the Credentials tab, click Add credential.
Give the credential a name, then click Save.
Carefully copy and save the client ID and client secret for your new credential.
Next, authorize the credential to access the necessary endpoints. Find the newly created credential in the list on the Credentials tab and click the three-dot menu, then select View details.
Enable GET on the API endpoints that display info on team members, loan officers, and loans.

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

Configure the nCino connector

To complete this task, you’ll need:
The Connector Administrator or Super Administrator role in ConductorOne
Access to the set of nCino 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 nCino and click Add.
Choose how to set up the new nCino 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 nCino credentials into the relevant fields.
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 nCino connector is now pulling access data into ConductorOne.

Follow these instructions to use the nCino 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 nCino connector

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

Secrets configuration

# baton-ncino-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-ncino-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>
  
  # nCino credentials
  BATON_NCINO_BASE_URL: <nCino API base URL>
  BATON_NCINO_CLIENT_ID: <nCino API client ID>
  BATON_NCINO_CLIENT_SECRET: <nCino API client secret>

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

Deployment configuration

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

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