Enrich professor profiles and harden client policy
This commit is contained in:
+16
-7
@@ -28,9 +28,11 @@ administrative incident overview for `AD`, the student information page for
|
||||
`AL`, or the portal menu for `DO`. After the incident page confirms an `AD`
|
||||
employee number, two additional GETs in the same in-memory session read the
|
||||
structured name from `datos/personales.aspx` and the address from
|
||||
`datos/ubicacion.aspx`. A supplemental failure preserves fields already
|
||||
collected, and a profile timeout does not invalidate an already authenticated
|
||||
credential. NTLM may still require its normal
|
||||
`datos/ubicacion.aspx`. Docentes keep the menu name as a base and attempt those
|
||||
same two shared staff modules without requiring them to exist. A supplemental
|
||||
404, changed/missing element ID, other failure, or timeout preserves fields
|
||||
already collected, and a profile timeout does not invalidate an already
|
||||
authenticated credential. NTLM may still require its normal
|
||||
challenge/response round trips on the connection. Transient portal cookies are
|
||||
kept only in an in-memory per-request container and are never persisted or
|
||||
returned to the client.
|
||||
@@ -60,9 +62,12 @@ updates the applicable `displayName`, `givenName`, `sn`, `mail`, `title`,
|
||||
`postalCode` attributes. Administrative and student numbers must match the six
|
||||
numeric digits of the requested identity before any role-specific metadata is
|
||||
trusted. Administrative personal and location pages are accepted only after
|
||||
that incident-page match. Student faculty/department is deliberately left unset because the
|
||||
verified page does not expose it. Missing metadata does not clear existing AD
|
||||
values and never changes the password outcome.
|
||||
that incident-page match. A docente's supplemental fields remain tied to the
|
||||
fresh NTLM-authenticated portal session and are optional; the menu display name
|
||||
remains usable if neither shared page is available. Student faculty/department
|
||||
is deliberately left unset because the verified page does not expose it.
|
||||
Missing metadata does not clear existing AD values and never changes the
|
||||
password outcome.
|
||||
|
||||
Human-readable SGU values are decoded with BOM/header/meta detection, strict
|
||||
UTF-8 validation, and a Windows-1252 fallback for the legacy portal. Names and
|
||||
@@ -91,7 +96,11 @@ synthetic Windows account to imitate that title or ordering.
|
||||
The managed hierarchy is rooted at `OU=Usuarios-SGU`: `Docentes`, `Alumnos`,
|
||||
and `Administrativos` are direct child OUs beneath it. The domain GPO
|
||||
`SGU - User session restrictions` is linked to this root and enables the
|
||||
per-user `DisableLockWorkstation` policy for the complete hierarchy.
|
||||
per-user `DisableLockWorkstation` policy and disables screen savers for the
|
||||
complete hierarchy. The computer GPO `SGU - Windows client experience` is linked
|
||||
to `OU=Laboratorio`; it suppresses first-logon/privacy/diagnostic prompts,
|
||||
disables location, and enforces always-on display, sleep, and hibernation
|
||||
settings for managed clients.
|
||||
|
||||
Per-user synchronization is serialized inside the broker to prevent concurrent
|
||||
create/reset races. Production deployments should run the broker as a gMSA with
|
||||
|
||||
Reference in New Issue
Block a user