-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.17.z
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
When `accessTokenInactivityTimeout` in the oauth config, only the OC login session gets logged out due to inactivity. It's not the case for web console login, it stays logged in even when the inactivity seconds go above the defined value in `accessTokenInactivityTimeout`
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
1. Set `accessTokenInactivityTimeout` in `oauth.spec.tokenConfig`. 2. Login again to the Web Console and leave it. 3. Wait till the defined value in `accessTokenInactivityTimeout`
Actual results:
The user session does not logout after inactivity.
Expected results:
The user session should log out after the timeout value.
Additional info:
- duplicates
-
OCPBUGS-35478 console never force user log out when accessTokenInactivityTimeoutSeconds reached
-
- ASSIGNED
-
-
OCPBUGS-53168 unhandled error: TypeError: L.b.logoutOpenShift is not a function
-
- Closed
-
- links to