Capabilities

Available hosting methods

Choose the hosting method that best suits your needs:

Gather Panther credentials

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

A user with the permission to make API tokens in Panther must perform this task.

Create a Panther API token

1. In Panther, click the gear icon in the top menu bar and select API Tokens.

2. Make a note of the API URL shown at the top of the page.

3. Click Create New Token.

4. Give the API token a name, such as “ConductorOne”.

5. Give the token the following permissions:

   • In the User Management section of the page, select Read User Info
   • In the Configuration section of the page, select Read Panther Settings Info
   • In the Supplementary section of the page, select Read API Token Info

6. Click Create API Token. The token is shown on a new page.

7. Carefully copy and save the token.

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

Set up a Panther cloud-hosted connector

To complete this task, you’ll need:

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

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

2. Search for Panther and click Add.

3. Choose how to set up the new Panther 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. In the API key and API URL fields, enter the credentials you created in Panther.

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

Set up a Panther cloud-hosted connector using Terraform

As an alternative to the cloud-hosted setup process described above, you can use Terraform to configure the integration between Panther and ConductorOne.

See the ConductorOne Panther integration resource page in the ConductorOne Terraform registry for example usage and the full list of required and optional parameters.

Set up a Panther self-hosted connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in ConductorOne
• Access to the set of Panther 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 Panther connector

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

2. Search for Baton and click Add.

3. Choose how to set up the new Panther 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 Panther connector deployment:

Secrets configuration

# baton-panther-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-panther-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>
  
  # Panther credentials
  BATON_TOKEN: <Panther API token>
  BATON_URL: <API URL of your Panther account>

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

Deployment configuration

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

3. Apply the deployment:

   kubectl -n conductorone apply -f baton-panther.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-panther}
   

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

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