Set up a Contentful connector

Capabilities
Gather Contentful credentials
Look up your organization ID
Create a CMA token
Configure the Contentful connector

Capabilities

Resource	Sync	Provision
Accounts
Teams
Organizations
Spaces

The Contentful connector supports automatic account provisioning. This connector does not support account deprovisioning. You must deprovision accounts directly in Contentful.

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 “C1”.

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 C1
Access to the set of Contentful credentials generated by following the instructions above

Cloud-hosted
Self-hosted

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

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

Search for Contentful 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 C1)
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 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.

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

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 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: Configure the Contentful connector

In C1, navigate to Integrations > 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 C1)
Add the connector to a managed app (select from the list of existing managed apps)
Create a new managed app

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-contentful-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-contentful-secrets
type: Opaque
stringData:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 client secret>
  
  # Contentful credentials
  BATON_TOKEN: <Contentful token>
  BATON_ORGANIZATION_ID: <Contentful org ID>

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

Step 3: Deploy the connector

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

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

Set up a Cloudflare Zero Trust connector

Set up a CouchDB connector

⌘I

Welcome

Manage connectors

Deploy connectors

Upload connector data

Configurable connectors

Pre-built connectors

Set up a Contentful connector

Capabilities

Gather Contentful credentials

Look up your organization ID

Create a CMA token

Configure the Contentful connector

Resources

Step 1: Configure the Contentful connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector

Welcome

Manage connectors

Deploy connectors

Upload connector data

Configurable connectors

Pre-built connectors

​Capabilities

​Gather Contentful credentials

​Look up your organization ID

​Create a CMA token

​Configure the Contentful connector

​Resources

​Step 1: Configure the Contentful connector

​Step 2: Create Kubernetes configuration files

​Secrets configuration

​Deployment configuration

​Step 3: Deploy the connector

Capabilities

Gather Contentful credentials

Look up your organization ID

Create a CMA token

Configure the Contentful connector

Resources

Step 1: Configure the Contentful connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector