Set up a Miro connector

Capabilities

Resource	Sync	Provision
Accounts
Teams
Roles

The Miro connector supports automatic account provisioning. This connector does not support account deprovisioning. You must deprovision accounts directly in Miro.

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 “C1 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

If you want to use C1 to provision access, also include:

team:write
organizations:team:write

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.

Optional: Generate a Miro SCIM access token

If you want to use C1 to provision accounts, you’ll also need a SCIM access token. If you haven’t already enabled SCIM for your Miro Enterprise account, follow the Miro documentation. To generate a new SCIM token:

Navigate to Company settings > Enterprise integrations.

In the SCIM Provisioning section, click Generate new token.

In the Generate new SCIM token modal, click Generate.

Carefully copy and save the SCIM token.

Done. 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 C1
Access to the set of Miro credentials generated by following the instructions above

Cloud-hosted
Self-hosted

Follow these instructions to use a built-in, no-code connector hosted by C1.

In C1, navigate to Apps > Connectors and click Add connector.

Search for Miro and click Add.

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.

Set the connector’s Name and, optionally, a Description.

Click the pencil icon next to Owners to choose who can configure and manage this connector.

Click Add. The connector is created and its configuration page opens.

Find the Settings area of the page and click Edit.

Paste the token into the Access token field.

Optional. If you want C1 to provision Miro accounts using this connector, paste the SCIM token into the SCIM 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.

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

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 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: Set up a new Miro connector

In C1, navigate to Apps > Connectors and click Add connector.

Search for Baton and click Add.

Set the connector’s Name and, optionally, a Description.

Click the pencil icon next to Owners to choose who can configure and manage this connector.

Click Add. The connector is created and its configuration page opens.

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:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 client secret>
  
  # Miro credentials
  BATON_MIRO_ACCESS_TOKEN: <Miro access token>

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

  # Optional: include if you want C1 to provision Miro accounts using this connector
  BATON_MIRO_SCIM_ACCESS_TOKEN: <Miro SCIM 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: public.ecr.aws/conductorone/baton-miro:latest
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-miro
        envFrom:
        - secretRef:
            name: baton-miro-secrets

Step 3: Deploy the connector

Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files.

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

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

Welcome

Manage connectors

Deploy connectors

Upload connector data

Configurable connectors

Pre-built connectors

Set up a Miro connector

Capabilities

Gather Miro credentials

Create a Miro app and generate an OAuth token

Optional: Generate a Miro SCIM access token

Configure the Miro connector

Resources

Step 1: Set up a new Miro connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector

​Capabilities

​Gather Miro credentials

​Create a Miro app and generate an OAuth token

​Optional: Generate a Miro SCIM access token

​Configure the Miro connector

​Resources

​Step 1: Set up a new Miro connector

​Step 2: Create Kubernetes configuration files

​Secrets configuration

​Deployment configuration

​Step 3: Deploy the connector

Capabilities

Gather Miro credentials

Create a Miro app and generate an OAuth token

Optional: Generate a Miro SCIM access token

Configure the Miro connector

Resources

Step 1: Set up a new Miro connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector