Set up a Contentful connector

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

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

1. In Contentful, click the environment switcher at the top of the page.

2. Click the organization’s name and select Organization settings & subscriptions.

3. Navigate to the Organization information tab. Carefully copy and save the Organization ID.

Create a CMA token

1. In Contentful, navigate to Settings > CMA tokens.

2. Click Create personal access token and give the new token a name, such as “C1”.

3. Click Generate. Carefully copy and save the new token.

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

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 Contentful 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. Paste the token into the Contentful API token field.

9. Paste the organization ID into into the Organization ID 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.

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

Self-hosted

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

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 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: public.ecr.aws/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

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

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