Skip to content
Connection Guide

Connect BlueCat Micetro Without Breaking the Audit Trail

Use this guide to connect BlueCat Micetro or confirm the export-based path that fits your environment. Aurora keeps source, timestamps, ownership, and collection history attached so the first run becomes reusable proof instead of one-off setup work.

Connector Summary
Connection typeDirect connection
CategoryDdi
Checklist4 steps
Want help with rollout?
We'll confirm what can be automated, what stays export-based, and how to keep the first evidence record clean.

First-Run Checklist

Use this sequence to connect BlueCat Micetro and make sure the first collection lands cleanly.

  1. 1
    Point base_url at the Micetro Web Services host that exposes /mmws/api/doc and /mmws/api/swagger.json.
  2. 2
    Store username and password for the dedicated read-only Micetro integration user.
  3. 3
    Set micetro_central_server only when Aurora must direct the Web Services tier at a non-local Micetro Central target.
  4. 4
    Validate the locally exposed swagger paths during onboarding and confirm the inferred history, logging, and inventory endpoints match the deployed Micetro version.

Credentials and Secrets

The keys, secrets, or tokens Aurora uses to authenticate and collect proof.

password

Recommended Access

Aurora only asks for the minimum read access needed for collection and checks.

Access requirements depend on the collection mode and scope you choose.