Details
-
Type:
Bug
-
Status:
Ready for QA
(View Workflow)
-
Priority:
Normal
-
Resolution: Unresolved
-
Component/s: NEP
-
Labels:None Labels
-
Customer:Airtel India
-
Complexity:Very High
-
Product:NEP
Description
Users are facing errors while logging out of NEP through ADFS. The logout process does not terminate the session properly, leading to session persistence issues.
This may also be contributing to the “User already authenticated” issue.
Steps to Reproduce:
Login to NEP via ADFS
Click on Logout
Observe behavior
Actual Result:
Error during logout (ADFS URL issue)
Session not terminated
Expected Result:
Successful logout without errors
Complete session termination (both NEP + ADFS)
Impact:
Sessions remain active
Users face login issues later
Security concern (session persistence)
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
- Transitions
- Trace
Fix: AppUserChecker.check() now evicts the stale cache entry instead of throwing on re-login. Also hardened adfsLogin() to swallow logout errors before calling validateToken.
Show
Omar Kamalddine
added a comment - Fix: AppUserChecker.check() now evicts the stale cache entry instead of throwing on re-login. Also hardened adfsLogin() to swallow logout errors before calling validateToken.
Root cause: Spring Security user cache was not evicted on SSO logout when the authentication field was null/stale after Vaadin session reset, causing AppUserChecker to block re-login with MultipleAuthenticationException.
Fix: AppUserChecker.check() now evicts the stale cache entry instead of throwing on re-login. Also hardened adfsLogin() to swallow logout errors before calling validateToken.