Set up a Lucidchart connector

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

Capabilities

Resource	Sync	Provision
Accounts		*
Folders
Documents

The Lucidchart connector supports automatic account provisioning.

*Account provisioning is only available on Lucidchart accounts with Enterprise licenses.

When a new account is created by C1, the account’s password will be sent to a vault.

This connector does not support account deprovisioning. You must deprovision accounts directly in Lucidchart.

Gather Lucidchart credentials

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

A user with access to the developer tools in Lucidchart must perform this task.

Create an API key

1. In the Lucidchart developer portal, navigate to API Keys.

2. Click + Create API Key.

3. Give the new key a name, such as “C1” and set an expiration, if desired.

4. Give the key the relevant set of grants:

   • To give C1 sync-only (READ) access: Documents - View and Folders - View

   • To give C1 provisioning (READ/WRITE) access: Documents - Edit and Folders - Edit

5. Click Generate API key. The new key is created.

6. Carefully copy and save the API key.

Create an OAuth2 client

1. Navigate to https://lucid.app/developer#/packages and click Create Application.

2. Give the new app a name, then click Create.

3. Select the new app’s OAuth 2.0 tab.

4. Enter https://accounts.conductor.one/oauth/callback in the Redirect URI field.

5. Click Create OAuth 2.0 client.

6. Carefully copy and save the OAuth client ID and client secret.

Self-hosted only: Create an OAuth refresh token

If you’re setting up a self-hosted Lucidchart connector, you’ll also need a refresh token for the Lucidchart OAuth client.

1. Follow the Lucidchart OAuth2 access token documentation to create an access token.

2. If you want to use the Lucidchart connector to provision accounts, give the token the account.user scope.

   Account provisioning is only available on Lucidchart accounts with Enterprise licenses.

3. Carefully copy and save the refresh token included in the token response.

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

Configure the Lucidchart connector

To complete this task, you’ll need:

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

   Don’t see the Lucidchart connector? Reach out to [e-mail] to add Lucidchart to your Connectors page.

3. Choose how to set up the new Lucidchart 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. Paste the API key in the Lucidchart API key field.

8. Paste the client ID and client secret into the relevant fields.

9. Optional. By default, the connector syncs Lucidchart documents and folders that are shortcuts. If you prefer not to sync shortcuts (because they don’t grant effective permissions or might return 403/404 errors from the API), click to enable Exclude shortcuts.

10. Click Save.

11. Click Login with OAuth.

12. Log into Lucidchart and authorize C1.

13. After authorizing, you’ll be redirected back to the C1 integrations page, where an “Authorized as” message is now printed.

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

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

Self-hosted

Follow these instructions to use the Lucidchart 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: Configure the Lucidchart 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 Lucidchart 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 Lucidchart connector deployment:

Secrets configuration

# baton-lucidchart-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-lucidchart-secrets
type: Opaque
stringData:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 client secret>
  
  # Lucidchart credentials
  BATON_LUCID_API_KEY: <Lucidchart API key>
  BATON_LUCID_CLIENT_ID: <Lucidchart OAuth2 client ID>
  BATON_LUCID_CLIENT_SECRET: <Lucidchart OAuth2 client secret>
  BATON_LUCID_REFRESH_TOKEN: <Lucidchart OAuth2 refresh token>

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

  # Options: include if you do not want to sync shortcuts 
  BATON_EXCLUDE_SHORTCUTS: true

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

Deployment configuration

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

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