Set up an Atlassian Confluence connector

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

This is an updated and improved version of the Confluence connector! If you’re setting up Confluence with C1 for the first time, you’re in the right place.

Capabilities

Resource	Sync	Provision
Accounts
Groups
Spaces
Space permissions
Space Roles (opt-in)
Space Role Assignments (opt-in)

To limit sync times, a limited list of Spaces entitlements and their associated grants are synced. See the Spaces entitlements synced by default section of this page for more information.

RBAC space roles

The Confluence connector supports two modes for syncing space access:

• Granular space permissions (default): Syncs individual noun-verb permission pairs (for example, read-space, administer-space) per space. This is the default behavior.
• RBAC space roles: Syncs Confluence’s built-in space roles and their assignments instead of granular permissions. Enable this mode by setting the --use-rbac flag (or BATON_USE_RBAC=true).

The connector uses one mode or the other — not both. When RBAC mode is enabled, granular space permissions are not synced, and the Space Roles and Space Role Assignments resource types become active.

RBAC mode requires that Space Roles are enabled and entitled on your Confluence instance. If the RBAC endpoints are unavailable (for example, because a trial or beta grant has expired), the connector’s Validate step fails with the message:

RBAC data endpoints are unavailable (space-roles returned 404) — this can happen when a trial or beta grant for RBAC has expired

If you see this error, either disable --use-rbac or contact Atlassian to ensure Space Roles are enabled on your instance.

Gather Confluence credentials

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

Important

A user with Administrator access in Confluence must perform this task.

Create an API token

1. Log into your Confluence account with Administrator access.

2. Navigate to https://id.atlassian.com/manage-profile/security/api-tokens.

3. Click Create API token.

4. Give your token a label, such as C1, and click Create.

5. Carefully copy and save the newly generated API token.

Done. Next, move on to the connector configuration instructions.

Configure the Confluence connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in C1
• Access to the set of Confluence 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 Integrations > Connectors and click Add connector.

2. Search for Confluence v2 and click Add.

3. Choose how to set up the new Confluence 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 C1)
   • 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 C1 users. Setting multiple owners is allowed. If you choose someone else, C1 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. Enter your Confluence domain (the URL of your Confluence instance is <YOUR DOMAIN>.atlassian.net) into the Confluence site domain field.

8. Enter the username for your Confluence account in the Username field.

9. Paste the API token into the API key field.

10. Optional. If want to sync information on Confluence users’ personal spaces and their permissions, uncheck the Skip syncing personal spaces and their permissions box.

11. Click Save.

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

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

Self-hosted

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

• Official download center: For stable binaries (Windows/Linux/macOS) and container images.

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

Step 1: Set up a new Confluence connector

1. In C1, navigate to Integrations > Connectors > Add connector.

2. Search for Baton and click Add.

3. Choose how to set up the new Confluence 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 C1)
   • 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 C1 users. Setting multiple owners is allowed.

   If you choose someone else, C1 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 Confluence connector deployment:

Secrets configuration

# baton-confluence-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-confluence-secrets
type: Opaque
stringData:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 client secret>

  # Confluence credentials
  BATON_DOMAIN_URL: <Confluence site domain URL (for example, https://your-domain.atlassian.net)>
  BATON_USERNAME: <Username for your Confluence account>
  BATON_API_KEY: <Confluence API token>

  # Optional: include if you want C1 to provision access using this connector
  BATON_PROVISIONING: true

  # Optional: include to skip syncing personal spaces and their permissions
  BATON_SKIP_PERSONAL_SPACES: true

  # Optional: include to use RBAC space roles instead of granular permissions
  # BATON_USE_RBAC: true

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

Deployment configuration

# baton-confluence.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-confluence
  labels:
    app: baton-confluence
spec:
  selector:
    matchLabels:
      app: baton-confluence
  template:
    metadata:
      labels:
        app: baton-confluence
        baton: true
        baton-app: confluence
    spec:
      containers:
      - name: baton-confluence
        image: public.ecr.aws/conductorone/baton-confluence:latest
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-confluence
        envFrom:
        - secretRef:
            name: baton-confluence-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 Confluence connector to. Confluence data should be found on the Entitlements and Accounts tabs.

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

Spaces entitlements synced by default

Each Confluence Space has its own set of permissions and allowed actions, which can result in a very large set of entitlement and grant access information in each Space.

The Confluence connector syncs entitlements formed by valid pairs of targets (nouns) and operators (verbs), such as administer-space or read-space.

When configuring the connector in C1, the noun and verb fields are pre-filled with a suggested subset (space noun and 6 common verbs). These suggested values only pre-populate the configuration form — they are not automatically applied. If you leave the noun and verb fields empty (or do not set --noun / --verb flags), the connector syncs all available nouns and verbs listed below.

All available targets (nouns):

• attachment
• blogpost
• comment
• page
• space

All available operators (verbs):

• administer
• archive
• create
• delete
• export
• read
• restrict_content
• update

Not all target-operator (noun-verb) pairs are valid.

To limit what the Confluence connector syncs to C1, use the --noun and --verb flags when setting up the Confluence connector in self-hosted mode, or configure the noun and verb fields in the C1 UI for cloud-hosted connectors. See the baton-confluence repo’s README for more information.

Space permission entitlements are only synced when RBAC mode is disabled (the default). When --use-rbac is enabled, the connector syncs Space Roles and Space Role Assignments instead. See RBAC space roles for details.