Unify AD and SGU sign-in in Acceso Institucional
This commit is contained in:
1 parent
2e972a06bd
commit
771dc60f7d
13 files changed
+151
-79
No files matched your search
@@ -13,24 +13,26 @@ Ready-to-run bootstrap packages are published on the
|
||||
|
||||
## Authentication contract
|
||||
|
||||
1. Windows presents one **La Salle** sign-in tile with `Usuario` and `Contraseña`.
|
||||
2. The user enters a `DO`, `AL`, or `AD` key and the current password once.
|
||||
3. The tile sends that exact pair over mutually authenticated TLS to the broker,
|
||||
which validates it against the institutional authority. Only an authoritative
|
||||
`401`/`403` rejects it.
|
||||
4. On every valid sign-in, the broker performs an idempotent Active Directory
|
||||
UPSERT: it creates or repairs the account, its role OU and group, supported
|
||||
profile fields, and the AD password using the password just validated.
|
||||
5. The Credential Provider serializes the original `SecureString` to Windows.
|
||||
1. Windows selects **Acceso Institucional** by default. The built-in
|
||||
Microsoft password provider stays available for recovery.
|
||||
2. Ordinary domain usernames go straight to Windows for Active Directory
|
||||
authentication. A `DO`, `AL`, or `AD` key is checked against SGU first.
|
||||
3. The tile sends recognized institutional keys and their exact passwords over
|
||||
mutually authenticated TLS. After SGU accepts the credential, the broker
|
||||
performs an idempotent Active Directory UPSERT: it creates or repairs the
|
||||
account, role OU and group, supported profile fields, and AD password.
|
||||
4. If SGU rejects the key or is unavailable, the unchanged credentials go to
|
||||
Windows. Existing AD accounts can authenticate there; unknown or misspelled
|
||||
accounts are rejected by Windows and are never created.
|
||||
|
||||
No derived password is created. Passwords are not written to a database, file,
|
||||
event log, application log, command line, or response.
|
||||
|
||||
This makes Active Directory the only Windows sign-in account while preserving
|
||||
automatic synchronization: if a person changes their institutional password,
|
||||
the next successful La Salle sign-in updates the domain password before Windows
|
||||
continues. A matching prefix alone never creates an account; the institutional
|
||||
authority must first accept the submitted password.
|
||||
the next successful Acceso Institucional sign-in updates the domain password
|
||||
before Windows continues. A matching prefix alone never creates an account;
|
||||
the institutional authority must first accept the submitted password.
|
||||
|
||||
For administrative accounts, profile enrichment first verifies the employee
|
||||
number against the incident overview, then reads the structured given names and
|
||||
|
||||
Reference in new issue
Block a user