Capabilities

Available hosting methods

Choose the hosting method that best suits your needs:

Gather Concur credentials

Each setup method requires you to pass in credentials generated in Concur. Gather these credentials before you move on.

A user with Admin access in Concur must perform this task.

Create a Concur app

1. In the Concur admin panel, navigate to the OAuth 2.0 Application Management page.

2. Click + Create New App.

3. Give the new app a name, such as “ConductorOne integration”, and add a description.

4. In the Grants/Scopes area of the page, add the following:

   Grants:

   • client_credentials

   Scopes:

   • USER
   • identity.user.core.read
   • identity.user.enterprise.read
   • spend.user.general.read

5. Click Submit. The system displays the new app’s client ID and client secret.

6. Carefully copy and save the client ID and client secret.

7. Also make note of the app’s geolocation, which is one of the following:

   • https://us2.api.concursolutions.com
   • https://us1.api.concursolutions.com
   • https://emea.api.concursolutions.com
   • https://cn.api.concursolutions.com

Generate a refresh token

1. Follow the Concur authentication documentation to make the following call to the Concur API, substituting in the geolocation as the base URI in the oauth2_base address, and filling in your Concur username and password, as well as the app’s client ID and secret:

   oauth2_base=https://us.api.concursolutions.com/oauth2
   username=<concur_username> eg. john.doe@gmail.com OR Company UUID
   password=<password> eg. password1 OR request token (24 hours)
   client_id=<clientId> eg. e01f725d-b4ce-4ce3-a664-b670cb5876cb0
   client_secret=<clientSecret> eg. 35c3bd92-fcb8-405e-a886-47ff3fba5664
   curl -X POST -H 'concur-correlationid: nameofapp' "$oauth2_base/v0/token" --data "username=$username&password=$password&grant_type=password&client_secret=$client_secret&client_id=$client_id"
   

2. The API will return an access token and a refresh token. Carefully copy and save the refresh token.

That’s it! Next, move on to the instructions for your chosen setup method.

Set up a Concur cloud-hosted connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in ConductorOne
• Access to the set of Concur credentials generated by following the instructions above

1. In ConductorOne, click Connectors > Add connector.

2. Search for Concur and click Add.

   Don’t see the Concur connector? Reach out to support@conductorone.com to add Auth0 to your Connectors page.

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

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

3. Click Next.

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

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

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

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

8. Click Save.

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

Set up a Concur self-hosted connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in ConductorOne
• Access to the set of Concur credentials generated by following the instructions above

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.

Why use Kubernetes? Kubernetes provides automated deployment, scaling, and management of your connectors. It ensures high availability and reliable operation of your connector services.

Step 1: Configure the 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>
  
  # Contact ConductorOne support for Concur-specific credentials

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):

   kubectl create namespace conductorone
   

2. Apply the secret configuration:

   kubectl -n conductorone apply -f baton-concur-secrets.yaml
   

3. Apply the deployment:

   kubectl -n conductorone apply -f baton-concur.yaml
   

Step 4: Verify the deployment

1. Check that the deployment is running:

   kubectl -n conductorone get pods
   

2. View the connector logs:

   kubectl -n conductorone logs -l app=baton-${baton-concur}
   

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