Nailing the Security Audit with RRCU

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

  • Sync user identities from Miro to ConductorOne

  • Resources supported:

    • Teams

Add a new Miro connector

This task requires either the Connector Administrator or Super Administrator role in ConductorOne.

  1. In ConductorOne, click Connectors > 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

    Do you SSO into Miro using your identity, SSO, or federation provider? If so, make sure to add the connector to the unmanaged Miro app that was created automatically when you integrated your provider with ConductorOne, rather than creating a new managed app.

  1. Set the owner for this connector. You can manage the connector yourself, or choose someone else. Setting multiple owners is allowed.

    A Miro connector owner must have the following permissions:

    • Connector Administrator or Super Administrator role in ConductorOne
    • Company Admin role in Miro
  1. Click Next.

Next steps

  • If you are the connector owner, proceed to Configure your Miro connector.

  • If someone else is the connector owner, ConductorOne will notify them by email that their help is needed to complete the setup process.

Configure your Miro connector

A user with the Connector Administrator or Super Administrator role in ConductorOne and Company Admin role in Miro must perform this task.

Step 1: 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. We’ll use it in Step 2.

Step 2: Add your Miro credential to ConductorOne

  1. In ConductorOne, navigate to the Miro connector by either:

    • Clicking the Set up connector link in the email you received about configuring the connector.

    • Navigate to Connectors > Miro (if there is more than one Miro listed, click the one with your name listed as owner and the status Not connected).

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

  3. Paste the token you generated in Step 1 into the Access token field.

  4. Click Save.

  5. The connector’s label changes to Syncing, followed by Connected. View the logs to ensure that information is syncing.

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

Configure the Miro integration using Terraform

As an alternative to the integration 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.