We had exactly the same problem when switching to Xalan 2.6 and I am almost sure that
this is an issue with Xalan which does not seem to accept null values in template
parameters (previous versions did).
When the JBoss XSLSubDeployer tries to transform the xxx-ds.xml by providing a null
value fo
In case of a web tier, you should configure the client-login module in
login-config.xml instead of auth.conf
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3826218#3826218";>View
the original post
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3826218>Reply
to the
You should keep the caching on. If you don't, the LoginModule will be called on every
request (and it seems that the JaasSecurityManager won't work without cache).
If you want to update the password/roles of users, you have to flush the cache through
JMX by calling
"jboss.security:service=JaasSe