ConductorOne docs

Set up a Miro connector

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

Capabilities

Resource	Sync	Provision
Accounts	✅
Teams	✅

Gather Miro credentials

Configuring the connector requires you to pass in credentials generated in Miro. Gather these credentials before you move on.

A user with the Company Admin role in Miro must perform this task.

Create a Miro app and generate an OAuth token

In Miro, click your avatar in the upper right corner and select Settings.
Click the Your apps tab.
Click Create new app.
Give the new app a name, such as “ConductorOne integration” and select a developer team. You can leave the Expire access token box unchecked.
Click Create app.
The newly created app’s page opens. Scroll down to Permissions and select the following:
- identity:read
- team:read

organizations:read
organizations:team:read

Click Install app and get OAuth token.
Select a team, then click Add.
Your app is installed, and the app’s access token is shown. Carefully and copy and save the OAuth token.

That’s it! Next, move on to the connector configuration instructions.

Configure the Miro connector

To complete this task, you’ll need:
The Connector Administrator or Super Administrator role in ConductorOne
Access to the set of Miro 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 Miro and click Add.
Choose how to set up the new Miro 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 token into the Access token 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 Miro connector is now pulling access data into ConductorOne.

Follow these instructions to use the Miro 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: Set up a new Miro connector

In ConductorOne, navigate to Connectors > Add connector.
Search for Baton and click Add.
Choose how to set up the new Miro 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 Miro connector deployment:

Secrets configuration

# baton-miro-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-miro-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>
  
  # Miro credentials
  BATON_MIRO_ACCESS_TOKEN: <Miro access token>

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

Deployment configuration

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

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