Uploaded image for project: 'Apache Knox'
  1. Apache Knox
  2. KNOX-2776 Concurrent Session Limit for UIs
  3. KNOX-2790

Split ConcurrentSessionVerifier.verifySessionForUser

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Critical
    • Resolution: Fixed
    • 2.0.0
    • 2.0.0
    • Server
    • None

    Description

      Currently, the ConcurrentSessionVerifier.verifySessionForUser does 2 things:

      • verifies the user if he/she is allowed to have another session
      • registers the given token into the concurrentSessionCounter map

      These 2 functionalities should be split:

      • boolean verifySessionForUser(String userName);
      • void registerToken(String userName, JWT token);

      With this split, in WebSSOResource, the session verification can be done before the token is actually created and token registration can be done after. It's important because it might be a security leak to generate tokens in advance that will not be used at all but, in case of token management is enabled, may fill up the disk/memory with unused tokens.

      Attachments

        Issue Links

          Activity

            People

              mrtnbalazs Marton Bal√°zs
              smolnar Sandor Molnar
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 50m
                  50m