Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-3111

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

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker Blocker
    • 3.0.0.Beta30
    • 3.0.0.Beta27
    • Security
    • None
    • 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

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

              jondruse@redhat.com Jiri Ondrusek
              jondruse@redhat.com Jiri Ondrusek
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: