Details
-
Bug
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Done
-
None
-
None
-
-
Core: F - Sprint 78
-
Prokopovych
Description
Overview:
It seems that the login functionality does neither take user deletion or deactivation status into consideration after the login has happened, leading to very long log-in sessions for users that should have lost their access to FOLIO.
Steps to Reproduce:
- Using one browser, login to FOLIO wit user account A.
- Using another browser logged in as another user with the right permissions or by using an API call, either remove the user from FOLIO, or deactivate the user.
Expected Results:
The first browser session is terminated or the user is prevented from performing actions in FOLIO afer a short ammount of time.
Actual Results:
The user may stay logged in for months.
TestRail: Results
Attachments
Issue Links
- clones
-
CHAL-100 Users that are deleted or deactivated can stay logged in in folio untill their token expires (=for a VERY long time)
-
- Closed
-
- is blocked by
-
MODAT-56 validate user deactivation when checking access token
-
- Closed
-
- relates to
-
FOLIO-1233 Implement refresh tokens
-
- Closed
-
-
FOLIO-2354 Spike: Identify a strategy to work with tokens
-
- Open
-