I worked around this by extending ConfiguredIdentityLoginModule. I overrode
initialize to create a new options Map from the old one, but with the password
decrypted, then call super.initialize().
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4197194#4197194
I had this same problem and solved it by instead extending
ConfiguredIdentityLoginModule. I overrode initialize() to fetch the password
from the options map, decrypt it, then make a new hashmap (the old one is
unmodifiable) with the options, replacing the password with the decrypted
version,
I am trying to do the exact same thing and having the exact same problem. Not
only is the exception completely useless, but there's no other logging taking
place. Even putting system.err.println() tombstones in the code for my custom
login module doesn't work. It's as if it can't find the class
So it appears that the issue is that there is some sort of security code in or
near SubjectActions that prevents our custom class from using it. Even if we
actually shove our class directly into jboss-jca.jar, we still get the same
error, so it's not a classloader issue.
Of course, the actual
