Set up a Lucidchart connector

ConductorOne provides identity governance and just-in-time provisioning for Lucidchart. Integrate your Lucidchart instance with ConductorOne 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.

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

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

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

In the Lucidchart developer portal, navigate to API Keys.
Click + Create API Key.
Give the new key a name, such as “ConductorOne” and set an expiration, if desired.
Give the key the relevant set of grants:
- To give ConductorOne sync-only (READ) access: Documents - View and Folders - View
- To give ConductorOne provisioning (READ/WRITE) access: Documents - Edit and Folders - Edit
Click Generate API key. The new key is created.
Carefully copy and save the API key.

Create an OAuth2 client

Navigate to https://lucid.app/developer#/packages and click Create Application.
Give the new app a name, then click Create.
Select the new app’s OAuth 2.0 tab.
Enter https://accounts.conductor.one/oauth/callback in the Redirect URI field.
Click Create OAuth 2.0 client.
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.

Follow the Lucidchart OAuth2 access token documentation to create an access token.
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.
Carefully copy and save the refresh token included in the token response.

That’s it! 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 ConductorOne
Access to the set of Lucidchart 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 Lucidchart and click Add.
Don’t see the Lucidchart connector? Reach out to support@conductorone.com to add Lucidchart to your Connectors page.
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 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 API key in the Lucidchart API key field.
Paste the client ID and client secret into the relevant fields.
Click Save.
Click Login with OAuth.
Log into Lucidchart and authorize ConductorOne.
After authorizing, you’ll be redirected back to the ConductorOne integrations page, where an “Authorized as” message is now printed.
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 Lucidchart connector is now pulling access data into ConductorOne.

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 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 Lucidchart connector

In ConductorOne, navigate to Connectors > Add connector.
Search for Baton and click Add.
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 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 Lucidchart connector deployment:

Secrets configuration

# baton-lucidchart-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-lucidchart-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne 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>

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: ghcr.io/conductorone/baton-lucidchart:latest
        imagePullPolicy: IfNotPresent
        envFrom:
        - secretRef:
            name: baton-lucidchart-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 Lucidchart connector to. Lucidchart data should be found on the Entitlements and Accounts tabs.

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