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

    • Bug
    • Resolution: Done
    • Blocker
    • 7.1.0.CR1
    • 7.1.0.ER2
    • 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

    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

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-3111 Legacy ldap realm, caching by access time doesn't "clear" timeout for already cached entry

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Resolved
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-12378 (7.1.0) Upgrade to WildFly Core to 3.0.1.Final-redhat

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Verified
          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-11350 (7.0.z) Legacy ldap realm, entry for non existing user are cached

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: