Set up a Contentful connector

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

Capabilities

Resource	Sync	Provision
Accounts	✅
Teams	✅	✅
Organizations	✅	✅
Spaces	✅	✅

Gather Contentful credentials

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

A user with the Administrator role in Contentful must perform this task.

Look up your organization ID

In Contentful, click the environment switcher at the top of the page.
Click the organization’s name and select Organization settings & subscriptions.
Navigate to the Organization information tab. Carefully copy and save the Organization ID.

Create a CMA token

In Contentful, navigate to Settings > CMA tokens.
Click Create personal access token and give the new token a name, such as “ConductorOne”.
Click Generate. Carefully copy and save the new token.

That’s it! Next, move on to the connector configuration instructions.

Configure the Contentful connector

To complete this task, you’ll need:
The Connector Administrator or Super Administrator role in ConductorOne
Access to the set of Contentful credentials generated by following the instructions above

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

In ConductorOne, navigate to Admin > Connectors and click Add connector.
Search for Contentful and click Add.
Don’t see the Contentful connector? Reach out to support@conductorone.com to add Contentful to your Connectors page.
Choose how to set up the new Contentful 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
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.
Click Next.
Find the Settings area of the page and click Edit.
Paste the token into the Contentful API token field.
Paste the organization ID into into the Organization ID field.
Click Save.
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 Contentful connector is now pulling access data into ConductorOne.

Follow these instructions to use the Contentful connector, hosted and run in your own environment.

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.

Step 1: Configure the Contentful connector

In ConductorOne, navigate to Connectors > Add connector.
Search for Baton and click Add.
Choose how to set up the new Contentful 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
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.
Click Next.
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 Contentful connector deployment:

Secrets configuration

# baton-atlassian-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-atlassian-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>
  
  # Contentful credentials
  BATON_TOKEN: <Contentful token>
  BATON_ORGANIZATION_ID: <Contentful org ID>

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

Step 3: Deploy the connector

Create a namespace in which to run ConductorOne connectors (if desired), then apply the secret config and deployment config files.
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 Contentful connector to. Contentful data should be found on the Entitlements and Accounts tabs.

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