Skip to content
Connection Guide

Connect Omnissa Horizon Without Breaking the Audit Trail

Use this guide to connect Omnissa Horizon 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
CategoryVdi
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 Omnissa Horizon and make sure the first collection lands cleanly.

  1. 1
    Create a dedicated Horizon administrator account with the documented `MACHINE_VIEW` and `GLOBAL_CONFIG_VIEW` permissions only.
  2. 2
    Store base_url, tls_mode, domain, username, and password securely and validate `/rest/login`, `/rest/config/v1/settings`, and `/rest/inventory/v9/machines` before enabling scheduled sync.
  3. 3
    Keep `/rest/external/v1/ad-users-or-groups` and `/rest/external/v1/audit-events` out of scope unless Omnissa publishes stronger privilege and retention guidance.
  4. 4
    Prefer certificate validation; only allow insecure TLS as an explicit tenant override for private test environments.

Credentials and Secrets

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

usernamepassword

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.