Source Identity (LDAP)
On-prem source identities (objectSid, ms-DS-ConsistencyGuid, UPN) for cross-domain joins.
What it does
Unlike ActiveDirectoryDiscovery (V1/V2), which uses the RSAT ActiveDirectory module (Get-ADUser - requires a domain-joined / DNS-resolvable context), this module binds raw LDAP via System.DirectoryServices.Protocols with an EXPLICIT DC endpoint + per-domain credentials. That makes it work against: - isolated lab DCs reachable only by IP, - non-domain-joined collector hosts, - cross-FOREST source domains that must use a SIMPLE bind (Negotiate referral hangs). Output feeds the already-built SID-map generator (appliance/identity/sidMapGenerator.ts) via the appliance:identity:plan seam.
How the app exposes it
The module feeds into the ACQI app's dedicated results view. From there, conflicts, dependencies, and readiness scores roll up into the deal workspace.
/discovered/source-identity-ldap Outputs
Each module produces a CSV with readiness and risk scores, evidence-source counts, and last-seen timestamps. The exact columns vary by module — the app's results view shows the live schema.