Description of problem:
In EAP 6, when using the SecureIdentityLoginModule to encrypt datasource passwords, the results are not cached by the JAAS cache. In EAP 5, the results are cached. This can lead to a performance issue.
The root cause appears to be that the EAP 6 JAAS cache does not allow for a JAAS cache key to be null.
The issue only occurs when the application that uses the datasource is not secured. In this situation, the principal is null when isValid() and updateCache() are called. When the application is secured, the results are cached. I think it is working because the result of the SecureIdentityLoginModule are cached using the authenticated user's principal as the cache key.
Use vault for encrypting the database password. This does not use a JAAS login module so the JAAS cache and login module are completely avoided.
Derek Horton <email@example.com> updated the status of jira SECURITY-803 to Resolved
Fix committed to:
Verified in 6.3.0.ER4