Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

User is automatically logged back in after fixed session timeout expires

Description

Precondition:

Make sure that the fixed session timeout value is lower than the idle session timeout value.

Fixed session timeout value can be updated by changing the “Client Session Idle“ value in Keycloak admin interface.
Idle session timeout value cannot be changed after deployment.

Steps to reproduce:

  1. Login to FSE Dry run 1 (https://crs-sandbox2.int.aws.folio.org)

  2. Open any application

  3. Wait for the fixed session timeout to be close to being expired

Expected result:
“Your session will end soon! …“ text (fixed session timeout text) is shown below the top navigation bar. When the timer reaches 0, a user is logged out and redirected to a login screen.

Actual result:
“Your session will end soon! …“ text (fixed session timeout text) is shown below the top navigation bar. When the timer reaches 0, a page is reloaded. Login screen is not shown.

Additional information:

  • Also reproducible on evrk2 No longer reproducible on evrk2 as of 9/6/2024

  • See examples:

 

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Attachments

5
  • 06 Sep 2024, 02:39 PM
  • 06 Sep 2024, 02:39 PM
  • 06 Sep 2024, 01:33 PM
  • 05 Sep 2024, 02:12 PM
  • 05 Sep 2024, 02:12 PM

Checklist

hide

Activity

Show:

Yauhen Viazau September 6, 2024 at 2:45 PM
Edited

, - I am closing this ticket. Please feel free to re-open if you think some work still needs to be done/deployed in scope of it (seeing as it is in Prep. Deployment). But it looks like the actual problem was with settings in Keycloak, on both affected envs.

Yauhen Viazau September 6, 2024 at 2:41 PM

Re-tested on FSE Dry run 1 (https://crs-sandbox2.int.aws.folio.org/ ) - works as expected Check Mark
The original issue was due to me improperly configuring fixed session timeout value in Keyloak. When all 4 parameters are set to the same value (as advised by developers), fixed session timeout works as expected, including logout and re-login.

See examples:

 

Yauhen Viazau September 6, 2024 at 1:34 PM
Edited

Issue is no longer reproducible on evrk2 (https://diku4.int.aws.folio.org ) Check Mark

Craig McNally September 5, 2024 at 8:37 PM

This has been fixed, but not yet backported to Q. is on it.

Yauhen Viazau September 5, 2024 at 2:22 PM

- please review/fix. Reproducible on both evrk2 (https://diku4.int.aws.folio.org/ ) and FSE Dry run 1 (https://crs-sandbox2.int.aws.folio.org )

Cannot Reproduce

Details

Assignee

Reporter

Labels

Priority

Story Points

Sprint

Development Team

Eureka

RCA Group

Third party component integration

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created September 5, 2024 at 2:06 PM
Updated September 30, 2024 at 11:17 AM
Resolved September 6, 2024 at 2:46 PM
TestRail: Cases
TestRail: Runs

Flag notifications