Capabilities

Available hosting methods

Choose the hosting method that best suits your needs:

Gather Jamf credentials

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

A user the Administrator role in Jamf Pro must perform this task.

(Optional) Create a service account

The ConductorOne Jamf Pro connector requires a username and password. If desired, you can set up a service account to be used for the connector.

1. Follow the instructions in the Jamf documentation for Creating a Jamf Pro User Account

2. Give the user you create full access to the Jamf Pro instance and the Administrator privilege set.

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

Set up a Jamf cloud-hosted connector

To complete this task, you’ll need:

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

1. In ConductorOne, click Connectors > Add connector.

2. Search for Jamf and click Add.

3. Choose how to set up the new Jamf 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 Instance URL field, enter the URL of your Jamf Pro instance.

8. Enter the username of the service account you created (or the username of a Jamf Pro user with Administrator permissions) into the Username field.

9. Enter the password associated with the username into the Password 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 Jamf connector is now pulling access data into ConductorOne.

Set up a Jamf 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 Jamf Pro and ConductorOne.

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

Set up a Jamf self-hosted connector

To complete this task, you’ll need:

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

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

2. Search for Baton and click Add.

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

Secrets configuration

# baton-jamf-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-jamf-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>
  
  # Jamf credentials
  BATON_INSTANCE_URL: <URL of your Jamf Pro instance>
  BATON_PASSWORD: <Password to the Jamf Pro account>
  BATON_USERNAME: <Username for the Jamf Pro account>

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

Deployment configuration

# baton-jamf.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-jamf
  labels:
    app: baton-jamf
spec:
  selector:
    matchLabels:
      app: baton-jamf
  template:
    metadata:
      labels:
        app: baton-jamf
        baton: true
        baton-app: jamf
    spec:
      containers:
      - name: baton-jamf
        image: ghcr.io/conductorone/baton-jamf:latest
        args: ["service"]
        imagePullPolicy: IfNotPresent
        envFrom:
        - secretRef:
            name: baton-jamf-secrets

Step 3: Deploy the connector

1. Create a namespace in which to run ConductorOne connectors (if desired):

   kubectl create namespace baton-jamf
   

2. Apply the secret configuration:

   kubectl -n baton-jamf apply -f baton-jamf-secrets.yaml
   

3. Apply the deployment:

   kubectl -n baton-jamf apply -f baton-jamf.yaml
   

Step 4: Verify the deployment

1. Check that the deployment is running:

   kubectl -n c1 get pods
   

2. View the connector logs:

   kubectl -n c1 logs -l app=baton-${baton-jamf}
   

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

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