Unify AD and SGU sign-in in Acceso Institucional

This commit is contained in:
alexrg committed 2026-09-22 16:00:16 -06:00
1 parent 2e972a06bd
commit 771dc60f7d
13 files changed
+151 -79

No files matched your search

+18 -15
View File
@@ -52,22 +52,24 @@ Broker timeout, TLS failure, 429, or 5xx
-> only the last AD password succeeds
```
An explicit `400` or `401` from the broker is different: the provider displays
an error and does not serialize the rejected credential.
An explicit `400` or `401` from SGU does not create or update an account. The
tile submits the unchanged credentials to Windows, which accepts them only if
they match an existing Active Directory account.
## Account synchronization
The visible Windows experience is a single **La Salle** sign-in tile with
`Usuario` and `Contraseña`; the institutional authority is not a separate tile
or second password prompt. The broker normalizes the username to uppercase and
accepts exactly two letters plus six digits. After the authority accepts the
submitted password, it searches `BaseDn` by `sAMAccountName`, creates the user
when absent, moves it to the mapped OU when required, sets `userPrincipalName`,
and passes that same submitted 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. A matching username pattern alone never provisions an
account.
The visible Windows experience is one **Acceso Institucional** sign-in tile,
selected by default, with `Usuario` and `Contraseña`. Ordinary usernames go
straight to Windows for domain authentication. A `DO`, `AL`, or `AD` key is
checked by the broker against SGU. After SGU accepts the submitted password,
the broker searches `BaseDn` by `sAMAccountName`, creates the user when absent,
moves it to the mapped OU when required, sets `userPrincipalName`, and passes
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 rejects the credential or is unavailable, the unchanged credentials go to
Windows; only an existing AD account can then authenticate. A matching username
pattern alone never provisions an account.
Before an account becomes usable, the broker applies explicit deny ACEs for the
Active Directory `Change Password` extended right to SELF and Everyone. Users
@@ -132,8 +134,9 @@ Windows client maps the group into its local **Remote Desktop Users** group.
Every synchronized user also receives `La Salle` in the AD
`company` attribute unless deployment configuration supplies another default.
The generic La Salle credential is rendered as a dedicated branded tile instead of
being grouped below the anonymous **Other user** tile. Machine policy assigns
The generic Acceso Institucional credential is rendered as a dedicated
branded tile instead of being grouped below the anonymous **Other user** tile.
Machine policy assigns
the provider CLSID as the default provider, hides the last signed-in identity, and
disables local-user enumeration while retaining the built-in Microsoft password
provider and its **Other user** recovery path. The computer GPO also applies