Unify La Salle sign-in experience
This commit is contained in:
1 parent
ba2aca5c2a
commit
42f405e69c
13 files changed
+96
-41
No files matched your search
@@ -13,20 +13,25 @@ Ready-to-run bootstrap packages are published on the
|
||||
|
||||
## Authentication contract
|
||||
|
||||
1. The Windows tile collects a `DO`, `AL`, or `AD` institutional key and a password.
|
||||
2. It sends that exact password over mutually authenticated TLS to the broker.
|
||||
3. The broker validates the same key/password pair against the lightweight SGU
|
||||
NTLM root. Only an authoritative `401`/`403` rejects the credential.
|
||||
4. After successful authentication, the broker makes a separately bounded,
|
||||
best-effort request for the minimum available SGU profile fields.
|
||||
5. On success, the broker creates or moves the AD user, updates the available
|
||||
name/mail/title/department/address metadata when available, and sets the AD password
|
||||
to the exact submitted password.
|
||||
6. The Credential Provider serializes the original `SecureString` to Windows.
|
||||
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.
|
||||
|
||||
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.
|
||||
|
||||
For administrative accounts, profile enrichment first verifies the employee
|
||||
number against the incident overview, then reads the structured given names and
|
||||
surnames from `datos/personales.aspx` and the postal address from
|
||||
|
||||
Reference in new issue
Block a user