Set up a Concur connector

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

1. In ConductorOne, navigate to Admin > Connectors and click Add connector.

2. Search for Concur and click Add.

3. Choose how to set up the new Concur 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

4. 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.

5. Click Next.

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

7. Select your Concur geolocation from the Base URL list.

8. Paste your Concur client ID and secret into the Client ID and Client Secret fields.

9. Paste your refresh token into the Refresh Token field.

10. Click Save.

11. 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 Concur connector is now pulling access data into ConductorOne.

Follow these instructions to use the Concur connector, hosted and run in your own environment. Contact ConductorOne’s support team to download the latest version of the connector.

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 Concur connector

1. In ConductorOne, navigate to Connectors > Add connector.

2. Search for Baton and click Add.

3. Choose how to set up the new Concur 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

4. 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.

5. Click Next.

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

7. 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 Concur connector deployment:

Secrets configuration

# baton-concur-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-concur-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>
  
  # Concur-specific credentials
  BATON_CONCUR_BASE_URL: <Concur base URL>
  BATON_CONCUR_CLIENT_ID: <Concur client ID>
  BATON_CONCUR_CLIENT_SECRET: <Concur client secret>
  BATON_CONCUR_REFRESH_TOKEN: <Concur refresh token>

  # Optional: include if you want ConductorOne 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-concur.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-concur
  labels:
    app: baton-concur
spec:
  selector:
    matchLabels:
      app: baton-concur
  template:
    metadata:
      labels:
        app: baton-concur
        baton: true
        baton-app: concur
    spec:
      containers:
      - name: baton-concur
        image: ghcr.io/conductorone/baton-concur:latest
        imagePullPolicy: IfNotPresent
        envFrom:
        - secretRef:
            name: baton-concur-secrets

Step 3: Deploy the connector

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

2. 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 Concur connector to. Concur data should be found on the Entitlements and Accounts tabs.

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