Limit reversible password storage to SGU accounts

This commit is contained in:
alexrg committed 2026-09-29 11:35:27 -06:00
1 parent 843a1956d6
commit 80baae1b54
13 files changed
+139 -34

No files matched your search

+8 -5
View File
@@ -68,15 +68,18 @@ that same password directly to ADSI `SetPassword`. This is an idempotent UPSERT
performed on every successful sign-in, so the next sign-in after an institutional
password change updates AD before Windows validates the interactive logon. If
SGU explicitly rejects the credential, the provider stops without trying AD.
If SGO accepts it but AD synchronization fails, the provider reports that
failure without trying a stale AD verifier. Only a genuine broker/SGO outage
If SGU accepts it but AD synchronization fails, the provider reports that
failure without trying a stale AD verifier. Only a genuine broker/SGU outage
uses the documented Windows cached-domain-credential fallback, for an existing
account. A matching username pattern alone never provisions an account.
The domain bootstrap creates a fine-grained password policy for the three SGU
role security groups. It allows the broker to record the exact password SGO
accepted, even when the normal domain complexity policy would reject it. It
does not relax password requirements for other domain accounts.
role security groups. It allows the broker to record the exact password SGU
accepted, including reversible storage, even when the normal domain complexity
policy would reject it. The domain default remains unchanged; per-user reversible
storage is enabled only for members of those three groups. AD rewrites an existing
password in reversible form only when the broker sets it after a successful SGU
sign-in. Do not apply the setting to unrelated domain accounts.
Before an account becomes usable, the broker applies explicit deny ACEs for the
Active Directory `Change Password` extended right to SELF and Everyone. Users