Why does the JAAS cache fail to cache the results of the SecureIdentityLoginModule in EAP 6?

Solution Verified - Updated -

Issue

Why does the JAAS cache fail to cache the results of the SecureIdentityLoginModule in EAP 6?

We defined a datasource using security domain and configured username and password in the login module of the security domain. During performance test, it shows that the login() call was repeatedly executed on each access. Further investigations shows that the cache in the JBossCached AuthenticationManager was not used at all and is the cause of the high CPU usage in performance testing.

Below is the security domain setting in our standalone.xml (with the actual DB username / encrypted value masked).

<subsystem xmlns="urn:jboss:domain:security:1.2">
  <security-domains>
    <security-domain name="EncryptedPassword" cache-type="default">
      <authentication>
        <login-module code="org.picketbox.datasource.security.SecureIdentityLoginModule" flag="required">
          <module-option name="username" value="xxxx"/>
          <module-option name="password" value="xxxx"/>
        </login-module>
      </authentication>
    </security-domain>
  </security-domains>
</subsystem>

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 6.0.1

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.