Set up a Cloudflare Zero Trust connector

C1 provides identity governance for Cloudflare Zero Trust. Integrate your Cloudflare Zero Trust instance with C1 to run user access reviews (UARs) and enable just-in-time access requests.

Capabilities

Resource	Sync	Provision
Accounts
Access groups
Roles

Gather Cloudflare Zero Trust credentials

Configuring the connector requires you to pass in credentials generated in Cloudflare Zero Trust. Gather these credentials before you move on.

A user with Super Administrator access in Cloudflare Zero Trust must perform this task.

Locate your Cloudflare Account ID

1. Log into your Cloudflare Super Administrator account and select Workers from the left nav.

2. On the Workers page, find your Account ID on the right side of the page.

3. Copy and save the Account ID.

Create an API Token

Alternative credential option: If you do not want to generate and use an API token for the integration, Cloudflare Zero Trust also accepts authentication via an API key and the corresponding account’s email address. Find your API keys by navigating to My Profile > API Tokens.

1. Click the user icon and select My Profile.

2. Click API Tokens on the left side, then click Create Token.

3. At the bottom of the page, in the Custom Token area, click Get started.

4. Fill out the Create Custom Token page as follows:

   1. Give the API token a name, such as C1

   2. Set the appropriate permissions for the API token:

      If you want to use C1 to provision Cloudflare Zero Trust groups and roles, set:

      • Account -> Account Settings -> Read
      • Account -> Access: Organizations, Identity Providers, and Groups -> Edit
      • Account -> Access: Apps and Policies -> Read
      • Account -> Access: Audit Logs -> Read

      Otherwise, set:

      • Account -> Account Settings -> Read
      • Account -> Access: Organizations, Identity Providers, and Groups -> Read
      • Account -> Access: Apps and Policies -> Read
      • Account -> Access: Audit Logs -> Read

   3. Click Continue to summary.

5. Click Create Token and copy the token generated for you.

Done. You should now have one of the following credentials sets:

• Account ID
• API token

OR

• Account ID
• The email address associated with your Cloudflare account
• Global API key

Next, move on to the instructions for your chosen setup method.

Configure the Cloudflare Zero Trust connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in C1
• Access to the set of Cloudflare Zero Trust credentials generated by following the instructions above

Cloud-hosted

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

1. In C1, navigate to Apps > Connectors and click Add connector.

2. Search for Cloudflare Zero Trust and click Add.

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

4. Set the connector’s Name and, optionally, a Description.

5. Click the pencil icon next to Owners to choose who can configure and manage this connector.

6. Click Add. The connector is created and its configuration page opens.

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

8. Choose how you’ll authenticate to Cloudflare Zero Trust:

   • Select API token, then enter the account ID into the Account ID field and paste the API token into the API token field.
   • Select Email + API key, then enter the account ID into the Account ID field, your email into the Email ID field, and your Global API key into the API key field.
9. Click Save.

10. The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.

Done. Your Cloudflare Zero Trust connector is now pulling access data into C1.

Self-hosted

Follow these instructions to use the Cloudflare Zero Trust 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 Cloudflare Zero Trust connector

1. In C1, navigate to Apps > Connectors and click Add connector.

2. Search for Baton and click Add.

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

4. Set the connector’s Name and, optionally, a Description.

5. Click the pencil icon next to Owners to choose who can configure and manage this connector.

6. Click Add. The connector is created and its configuration page opens.

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

8. 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 Cloudflare Zero Trust connector deployment:

Secrets configuration

# baton-cloudflare-zero-trust-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-cloudflare-zero-trust-secrets
type: Opaque
stringData:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 client secret>
  
  # Cloudflare Zero Trust credentials, option 1
  BATON_ACCOUNT_ID: <Cloudflare Zero Trust account ID>
  BATON_API_TOKEN: <Cloudflare Zero Trust API token>

  # Cloudflare Zero Trust credentials, option 2
  BATON_ACCOUNT_ID: <Cloudflare Zero Trust account ID>
  BATON_API_KEY: <Cloudflare Zero Trust global API key>
  BATON_EMAIL: <Email address for your Cloudflare Zero Trust account>

  # Optional: include if you want C1 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-cloudflare-zero-trust.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-cloudflare-zero-trust
  labels:
    app: baton-cloudflare-zero-trust
spec:
  selector:
    matchLabels:
      app: baton-cloudflare-zero-trust
  template:
    metadata:
      labels:
        app: baton-cloudflare-zero-trust
        baton: true
        baton-app: cloudflare-zero-trust
    spec:
      containers:
      - name: baton-cloudflare-zero-trust
        image: public.ecr.aws/conductorone/baton-cloudflare-zero-trust:latest
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-cloudflare-zero-trust
        envFrom:
        - secretRef:
            name: baton-cloudflare-zero-trust-secrets

Step 3: Deploy the connector

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

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

Done. Your Cloudflare Zero Trust connector is now pulling access data into C1.