Done
Details
Assignee
Hongwei JiHongwei JiReporter
Jakub SkoczenJakub SkoczenLabels
Priority
P2Story Points
3Sprint
NoneDevelopment Team
Core: PlatformFix versions
TestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Hongwei Ji
Hongwei JiReporter
Jakub Skoczen
Jakub SkoczenLabels
Priority
Story Points
3
Sprint
None
Development Team
Core: Platform
Fix versions
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created November 18, 2019 at 1:08 PM
Updated April 2, 2021 at 1:48 PM
Resolved November 26, 2019 at 3:33 PM
This is one of the proposed solutions to (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.