Skip to content

History / Active Directory Import

Revisions

  • Document importing Windows hosts from Active Directory Adds Active Directory Import, and updates the pages that the feature changes. The new page leads with the part that is not obvious from the requirement: the preview is persisted server-side and apply may only subtract from it, because a WindowsTarget row makes DAD connect out to a named host carrying a domain credential. It also records the three query behaviours that are load-bearing (paging against AD's silent 1000-object cap, unclassifiable operating systems, domain controllers), the two-credential model, and what is and is not covered by CI. Home: the feature is the most recent pass, and the chronology now reads in order -- the Windows-source paragraph no longer claims to be "the most recent". Access Control: new section on why two controllers are Admin-only at the controller level, where reads are gated, unlike windows_targets. Corrects hidden? to a class method. Development: the two remote integrations and the seams they sit behind; suite counts corrected to 581 + 40 runs / 1969 assertions. Interface: the connection screens and the two-page import, including which rows arrive pre-checked and which do not. Installation: DAD_AR_ENCRYPTION_* and WINDOWS_SSL_VERIFY now name the second model that reads them; one variable covers the LDAPS and WinRM trust decision rather than two. Windows Events: cross-links, and the LDAP gap added to "limits worth knowing". What Changed Since 2016: new dated section, and the system-suite assertion count corrected to 247. Every claim here was checked against the code. Two were wrong as first written and corrected: the LDAPS/StartTLS note is on the show page, not the index, and the import result lands on the Windows targets screen. Co-authored-by: openhands <openhands@all-hands.dev>

    @openhands-agent openhands-agent committed Nov 11, 2026