Details
-
Bug
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Done
-
None
-
-
CP: sprint 77
-
3
-
Core: Platform
Description
This is one of the proposed solutions to UIU-1324 (the other being implementing support for refresh tokens in the UI/Stripes).
The idea is to validate user deactivation (and potentially other user properties, e.g expiration or removal) at the time the token is checked in mod-authtoken. This would be similar to how permissions are enforced.
The benefit of this approach is that it can be introduced transparently to the FOLIO UI and other clients (e.g edge modules).
The disadvantage is that it would impose additional performance penalty on the auth check operation – to limit this penalty we would need to cache the user record between auth checks.
TestRail: Results
Attachments
Issue Links
- blocks
-
UIU-1324 Users that are deleted or deactivated can stay logged in in folio until their token expires (=for a VERY long time)
-
- Closed
-
- relates to
-
FOLIO-1233 Implement refresh tokens
-
- Closed
-
-
FOLIO-2366 The folio-testing-backend builds fail, missing dependency mod-authtoken requires users
-
- Closed
-
-
MODAT-58 Do NOT check user for dummy token
-
- Closed
-
-
MODLOGSAML-92 SSO Logout does not destroy SAML session
-
- Closed
-
-
MODLOGSAML-94 Provide SLO (Single Log Out) endpoint to be called by SSO IdP
-
- Closed
-
-
STCOR-532 Logout from FOLIO, keep SSO login
-
- Closed
-