Skip to content
Connection Guide

Connect Foxpass Cloud LDAP Without Breaking the Audit Trail

Use this guide to connect Foxpass Cloud LDAP 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
CategoryIdentity
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 Foxpass Cloud LDAP and make sure the first collection lands cleanly.

  1. 1
    Create a dedicated Read-Only Foxpass API key and store it as api_token.
  2. 2
    Use https://api.foxpass.com/v1 as the default base_url unless the tenant is on a vendor-confirmed dedicated or self-hosted deployment.
  3. 3
    Validate users, groups, policy-bearing surfaces, and log endpoints in a sanctioned tenant before enabling scheduled sync.
  4. 4
    Keep conservative polling and backoff in place because Foxpass does not publish a public rate-limit or retry contract for these endpoints.

Credentials and Secrets

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

api_token

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.