Miro
  • 16 Sep 2024
  • 2 Minutes to read
  • Dark
    Light
  • PDF

Miro

  • Dark
    Light
  • PDF

Article summary

Miro is a digital collaboration platform designed to facilitate remote and distributed team communication and project management.

NOTE

This adapter is only for the Miro Enterprise plan.

Types of Assets Fetched

This adapter fetches the following types of assets:

  • Users
  • Roles
  • Groups
  • Licenses
  • Application Settings - (To fetch this info you need to configure the User name and Password fields. If 2FA is required for this application, the 2FA key must be provided.)
  • SaaS Applications

Parameters

  1. Host Name or IP Address (required) - The hostname or IP address of the Miro server. If Miro is not self-hosted, the Host Name must be https://api.miro.com.

  2. Client ID and Client Secret (required) - Miro Authentication credentials. Refer to Get started with OAuth2.0 and Miro.

  3. One Time OAuth Access Code - The one-time authentication code to get the refresh token. Refer to Generate the One Time OAuth Access Code below.

  4. User Name and Password (only for accounts with SaaS Management capability) - The credentials for a user account that has the permissions to fetch assets.

  5. 2FA Secret Key- (only for accounts with SaaS Management capability) - If you access Miro through an SSO solution that requires multi-factor authentication, you will need to generate a secret key in that solution and paste it here. See Set Up Google Authenticator in for the Okta adapter, for an example.

  6. Verify SSL - Select whether to verify the SSL certificate of the server against the CA database inside of Axonius. For more details, see SSL Trust & CA Settings.

  7. HTTPS Proxy (optional) - Connect the adapter to a proxy instead of directly connecting it to the domain.

  8. HTTPS Proxy User Name (optional) - The user name to use when connecting to the value supplied in Host Name or IP Address via the value supplied in HTTPS Proxy.

  9. HTTPS Proxy Password (optional) - The password to use when connecting to the server using the HTTPS Proxy.

To learn more about common adapter connection parameters and buttons, see Adding a New Adapter Connection.

Miro_Adapter2

APIs

Axonius uses the Miro REST API In Miro's Enterprise plan.

Required Permissions

The value supplied in Client ID must be associated with credentials that have appropriate Miro scopes as required in order to fetch SaaS data.

Adapter Integration Setup

NOTE

These instructions are relevant for users with Axonius Cyber-Security Asset Management capabilities, SaaS Management capabilities, or both.

Create an App in Miro

To create an app in Miro, ensure that your Miro user has a Developer team.

  1. From within a Miro account, click the account avatar to open the profile menu.

  2. Select Settings.

  3. Click the Your apps tab.

  4. Click + Create new app.
    CreateNewApp

  5. Enter an app name (for example: Axonius SaaS Management).

  6. Click Create App.
    CreateApp

Add Redirect URI for OAuth2.0

  1. On the App Settings page, locate the Redirect URI for OAuth2.0 section
  2. Enterthe following redirect URI: "https://localhost/adapters/miro_adapter"
  3. Click Add.
    RedirectURI

Set App Permissions

  1. On the App Settings page, locate the App URL section.
  2. In the Permissions area, select the following permissions:
    • identity:read
    • team:read
    • organizations:read
    • organizations:teams:read
  3. Click Install app and get OAuth token.

Generate the One Time OAuth Access Code

  1. Navigate to the following URL (make sure you add in your client ID to the URL):
    https://miro.com/oauth/authorize?response_type=code&client_id=Your_Client_ID&redirect_uri=https://localhost/adapters/miro_adapter

  2. On the dialog that opens, from the team drop-down list, select the relevant team.

  3. Click Add.The browser redirects to Axonius.

  4. Copy the "code" parameter from the browser's address bar.
    AUthenticationParameter

  5. Paste the copied parameter into the One Time OAuth Access Code field in the Axonius configuration.

Supported From Version

Supported from Axonius version 5.0



Was this article helpful?

What's Next