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

(7.1.0) Infinispan cache configuration is not always applied to security-domain

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 7.1.0.DR16
    • 7.0.4.GA
    • Security

      On EAP 7.0.4, I have the following standalone.xml :

              <subsystem xmlns="urn:jboss:domain:infinispan:4.0">
                  ...(snip)...
                  <cache-container name="security" default-cache="auth-cache">
                      <local-cache name="other">
                          <eviction strategy="LRU" max-entries="100"/>
                          <expiration lifespan="60000" max-idle="30000"/>
                      </local-cache>
                  </cache-container>
              </subsystem>
              ...(snip)...
              <subsystem xmlns="urn:jboss:domain:security:1.2">
                  <security-domains>
                      <security-domain name="other" cache-type="infinispan">
                          <authentication>
                              <login-module code="UsersRoles" flag="optional">
                                  <module-option name="password-stacking" value="useFirstPass"/>
                                  <module-option name="usersProperties" value="${jboss.server.config.dir}/users.properties"/>
                                  <module-option name="rolesProperties" value="${jboss.server.config.dir}/roles.properties"/>
                              </login-module>
                          </authentication>
                      </security-domain>
      

      Once a user is authenticated in the "other" security-domain, its username and credential is stored in inifinispan cache but never be expired.

              pferraro@redhat.com Paul Ferraro
              rhn-support-hokuda Hisanobu Okuda
              Ondrej Kotek Ondrej Kotek
              Ondrej Kotek Ondrej Kotek
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: