Set up Whimsical connector

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

Capabilities

Resource	Sync	Provision
Users
Roles

The Whimsical connector syncs users and roles via the SCIM 2.0 API.

This connector supports the following provisioning operations:

• User account provisioning: Create new users via SCIM POST
• User account deletion: Remove users from the workspace via SCIM DELETE
• Role provisioning: Assign and revoke Editor or Viewer roles via SCIM PATCH (grant/revoke)

Requirements

• A Whimsical Enterprise plan with SAML SSO enabled
• A SCIM OAuth token from workspace settings

Gather Whimsical credentials

Obtain a SCIM OAuth token

1. Log in to Whimsical as a workspace administrator.

2. Click on the workspace name in the top left corner.
3. Navigate to Workspace settings.
4. Ensure SAML SSO is enabled and correctly configured.
5. Enable SCIM provisioning.
6. Click Reveal to retrieve the OAuth token.
7. Copy the token immediately.

See the Whimsical SCIM documentation for detailed instructions.

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

Configure the Whimsical connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in C1
• Your Whimsical SCIM OAuth token generated 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 Whimsical and click Add.

3. Choose how to set up the new Whimsical connector:

   • Add the connector to a currently unmanaged app
   • Add the connector to a managed app
   • Create a new managed app
4. Set the owner for this connector and click Next.

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

6. Paste the SCIM OAuth Token.

7. Click Save.

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

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

Self-hosted

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

Secrets configuration

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

  # Whimsical config
  BATON_WHIMSICAL_TOKEN: <Whimsical Token>

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

Deployment configuration

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

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

---

All versions of this connector are available at dist.conductorone.com.