Project

General

Profile

Actions

Bug #29270

closed

Implement refresh token mechanism for SSO

Added by Rahul Bajaj about 4 years ago. Updated almost 4 years ago.

Status:
Duplicate
Priority:
Normal
Assignee:
Category:
Authentication
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

Related issues 1 (0 open1 closed)

Is duplicate of Foreman - Bug #29744: Consistent session expiry for oidc external usersClosedRahul BajajActions
Actions #1

Updated by Rahul Bajaj about 4 years ago

Description of problem:
If Access Token Lifespan is set to 5 mins then the user is getting sign out instead after idle SSO timeout

Version-Release number of selected component (if applicable):
Satellite 6.7 Snap 10

How reproducible:
Always

Steps to Reproduce:
1. Setup the Satellite with RHSSO instance and Keep Access Token Lifespan = 5 min
2. Keep SSO Session Idle = 30 mins
3. Setup the Smart Card with firefox browser and login using a smart card in Satellite
4. Go Idle for 5 mins
5. User is getting Signout from the application after 5 mins instead of 30 mins of idle session

Actual results:
User is getting Signout

Expected results:
User should not get Signout

Additional info:
This seems to be an issue with a refresh token if JWT token got expired, need to renew with the use of Refresh Token.

Actions #2

Updated by Rahul Bajaj almost 4 years ago

  • Status changed from Assigned to Closed
Actions #3

Updated by Tomer Brisker almost 4 years ago

  • Status changed from Closed to Duplicate

marking as duplicate, as the issue was resolved by #29744

Actions #4

Updated by Tomer Brisker almost 4 years ago

  • Is duplicate of Bug #29744: Consistent session expiry for oidc external users added
Actions

Also available in: Atom PDF