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
+8
-6
@@ -87,13 +87,15 @@ Use an enterprise CA with revocation checking in production.
|
||||
|
||||
## Recovery and availability
|
||||
|
||||
The provider distinguishes an authoritative rejection from unavailable
|
||||
infrastructure:
|
||||
The provider distinguishes an SGU rejection from unavailable infrastructure:
|
||||
|
||||
- `400`/`401`: fail closed and show an error.
|
||||
- timeout, TLS/connectivity error, `429`, or `5xx`: submit the unchanged credential
|
||||
to Windows. Windows must still validate it against AD or the cached domain
|
||||
verifier, so this does not grant access without the last synchronized password.
|
||||
- `400`/`401`: do not create or update the account; submit the unchanged
|
||||
credential to Windows so an existing AD account can authenticate.
|
||||
- timeout, TLS/connectivity error, `429`, or `5xx`: submit the unchanged
|
||||
credential to Windows. Windows must still validate it against AD or its cached
|
||||
domain verifier, so this does not grant access without a domain credential.
|
||||
- usernames that do not match the institutional key format go directly to
|
||||
Windows and are never sent to SGU or provisioned by the broker.
|
||||
|
||||
Redis is deliberately not used for password continuity. A second persistent
|
||||
password verifier duplicates attackable credential material, while a reversible
|
||||
|
||||
Reference in new issue
Block a user