Capabilities

Available hosting methods

Choose the hosting method that best suits your needs:

Gather Miro credentials

Each setup method 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

1. In Miro, click your avatar in the upper right corner and select Settings.

2. Click the Your apps tab.

3. Click Create new app.

4. Give the new app a name, such as “ConductorOne integration” and select a developer team. You can leave the Expire access token box unchecked.

5. Click Create app.

6. The newly created app’s page opens. Scroll down to Permissions and select the following:

   • identity:read
   • team:read

• organizations:read
• organizations:team:read

1. Click Install app and get OAuth token.

2. Select a team, then click Add.

3. 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 instructions for your chosen setup method.

Set up a Miro cloud-hosted 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

1. In ConductorOne, navigate to Admin > Connectors and click Add connector.

2. Search for Miro and click Add.

3. 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

4. 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.

5. Click Next.

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

7. Paste the token into the Access token field.

8. Click Save.

9. 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.

Set up a Miro cloud-hosted connector using Terraform

As an alternative to the cloud-hosted setup process described above, you can use Terraform to configure the integration between Miro and ConductorOne.

See the ConductorOne Miro integration resource page in the ConductorOne Terraform registry for example usage and the full list of required and optional parameters.

Set up a Miro self-hosted 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

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.

Why use Kubernetes? Kubernetes provides automated deployment, scaling, and management of your connectors. It ensures high availability and reliable operation of your connector services.

Step 1: Configure the Miro connector

1. In ConductorOne, navigate to Connectors > Add connector.

2. Search for Baton and click Add.

3. 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

4. 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.

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

1. Create a namespace in which to run ConductorOne connectors (if desired):

   kubectl create namespace conductorone
   

2. Apply the secret configuration:

   kubectl -n conductorone apply -f baton-miro-secrets.yaml
   

3. Apply the deployment:

   kubectl -n conductorone apply -f baton-miro.yaml
   

Step 4: Verify the deployment

1. Check that the deployment is running:

   kubectl -n conductorone get pods
   

2. View the connector logs:

   kubectl -n conductorone logs -l app=baton-${baton-miro}
   

3. 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.