Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-12370

[7.1] Legacy ldap realm, caching by access time doesn't "clear" timeout for already cached entry

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Verified (View Workflow)
    • Priority: Blocker
    • Resolution: Done
    • Affects Version/s: 7.1.0.ER2
    • Fix Version/s: 7.1.0.CR1
    • Component/s: Security
    • Labels:
      None
    • Target Release:
    • Steps to Reproduce:
      Hide

      See https://issues.jboss.org/browse/JBEAP-9391 for more details.

      1 - configure accessByTime cache for ldap authentication, for for example 60 seconds
      2 - authenticate as 'user01' in time t
      3 - re-authenticate as 'user01' in time t + 30s

      Expected result: user01 wil be evicted in time t + 90s, but it is evicted in time t + 60s

      Show
      See https://issues.jboss.org/browse/JBEAP-9391 for more details. 1 - configure accessByTime cache for ldap authentication, for for example 60 seconds 2 - authenticate as 'user01' in time t 3 - re-authenticate as 'user01' in time t + 30s Expected result: user01 wil be evicted in time t + 90s, but it is evicted in time t + 60s

      Description

      If ldap cache by access time is used cached entry will be evicted by timeout even if it is accessed again within timeout interval.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              jondruse Jiri Ondrusek
              Reporter:
              jondruse Jiri Ondrusek
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: