Miradore
Purpose
Synchronises devices, users, organizations, locations, tags, and configuration profiles from Miradore MDM, so managed endpoints and the people they belong to appear alongside the rest of your inventory.
tip
Secret fields below accept either an AWS Secrets Manager ARN or a value pasted directly into SubImage's managed vault. See Secrets for details.
Required Fields
| Field | Secret? | Description |
|---|---|---|
miradore_site_name |
No | The <site> segment of your Miradore URL, https://online.miradore.com/<site> |
miradore_api_key |
Yes | Miradore API v1 key: its AWS Secrets Manager ARN, or the value pasted into the vault |
miradore_base_uri |
No | Miradore base URI (default https://online.miradore.com) |
Setup Steps
- Sign in to the Miradore web console as an administrator.
- Go to System → Infrastructure diagram, hover over the API icon, and click Create key.
- Give the key a descriptive name such as
subimageand create it. Copy the value immediately: Miradore never displays it again. - Note your site name. It is the segment after the host in your console URL, so
https://online.miradore.com/acmemeans the site name isacme. - In SubImage, set
miradore_site_nameandmiradore_api_key(the key or its AWS Secret ARN), then save the module.
Notes
- The sync is read-only and uses Miradore API v1. API v2 exposes no endpoints for listing inventory.
- The site name scopes every node's identity, so devices numbered identically in two Miradore sites stay distinct in the graph.
- Miradore devices can feed the canonical
Deviceontology alongside other MDM sources such as Jamf and Kandji.
Troubleshooting
Sync fails with 401. The API key is invalid or was revoked. Create a new key and update the module configuration.
Sync fails with 404. No Miradore site matches miradore_site_name. Check the segment in your console URL.
Sync reports an unexpected Miradore response. Miradore answered with a web page instead of an API document, which usually means the site name or the key is wrong. Verify both.