Set up a Percipio connector

Capabilities

Resource	Sync	Provision
Accounts
Courses

Gather Percipio credentials

Configuring the connector requires you to pass in credentials generated in Percipio. Gather these credentials before you move on. To set up the integration with C1, you’ll need:

Your Percipio organization UUID
The API bearer token associated with a Percipio service account

Please work with your Skillsoft Account Team to set up a service account for the C1 integration and gather these credentials. Done. Next, move on to the connector configuration instructions.

Configure the Percipio connector

To complete this task, you’ll need:

The Connector Administrator or Super Administrator role in C1
Access to the set of Percipio credentials generated by following the instructions above

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

In the Organization ID field, enter your Percipio organization UUID.

In the API Token field, enter the token associated with the Percipio service account set up for this integration.

Optional. In the Course IDs field, add the ID numbers of the courses you want to sync. If no course numbers are entered, C1 will sync all available courses.

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 Percipio connector is now pulling access data into C1.

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

GitHub repository: Access the source code, report issues, or contribute to the project.

Step 1: Set up a new Percipio connector

In C1, navigate to Apps > Connectors and click 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. We’ll use them in Step 2.

Step 2: Create Kubernetes configuration files

Create two Kubernetes manifest files for your Percipio connector deployment:

Secrets configuration

# baton-percipio-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-percipio-secrets
type: Opaque
stringData:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 client secret>
  
  # Percipio credentials
  BATON_API_TOKEN: <Percipio API bearer token>
  BATON_ORGANIZATION_ID: <Percipio organization ID>
  BATON_LIMITED_COURSES: <Optional. Limit synced courses to the course IDs you specify here>

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

Deployment configuration

# baton-percipio.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-percipio
  labels:
    app: baton-percipio
spec:
  selector:
    matchLabels:
      app: baton-percipio
  template:
    metadata:
      labels:
        app: baton-percipio
        baton: true
        baton-app: percipio
    spec:
      containers:
      - name: baton-percipio
        image: public.ecr.aws/conductorone/baton-percipio:latest
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-percipio
        envFrom:
        - secretRef:
            name: baton-percipio-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 Apps. On the Managed apps tab, locate and click the name of the application you added the Percipio connector to. Percipio data should be found on the Entitlements and Accounts tabs.

Done. Your Percipio connector is now pulling access data into C1.

Welcome

Manage connectors

Deploy connectors

Upload connector data

Configurable connectors

Pre-built connectors

Set up a Percipio connector

Capabilities

Gather Percipio credentials

Configure the Percipio connector

Resources

Step 1: Set up a new Percipio connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector

​Capabilities

​Gather Percipio credentials

​Configure the Percipio connector

​Resources

​Step 1: Set up a new Percipio connector

​Step 2: Create Kubernetes configuration files

​Secrets configuration

​Deployment configuration

​Step 3: Deploy the connector

Capabilities

Gather Percipio credentials

Configure the Percipio connector

Resources

Step 1: Set up a new Percipio connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector