L3 Support
  1. L3 Support
  2. LS-1027

NEP Logout via ADFS – Session Not Terminating Properly (ADFS URL Error)

        Details

        • Type: Bug Bug
        • Status: Ready for QA Ready for QA (View Workflow)
        • Priority: Normal 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

            Ascending order - Click to sort in descending order
            Hide
            Permalink
            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.

            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.
            Hide
            Permalink
            Omar Kamalddine added a comment -

            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.

            Show
            Omar Kamalddine added a comment - 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.
            Cancel

              People

              • Assignee:
                Sanju Yadav
                Reporter:
                Sanju Yadav
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Due:
                  Created:
                  Updated:
                  Planned Start:
                  Planned End:

                  Drag and Drop