The only security service I see via jmx-console is
jboss.security
* service=JaasSecurityManager
I'm missing SecurityConfig and XMLLoginConfig,
which should both be there since they have @JMX.
They get picked up, and instantiated, but that's as far as it goes.
2008-08-07 15:50:16,734 DEBUG
[org.jboss.deployers.structure.spi.helpers.AbstractDeploymentContext]
(main) Added component XMLLoginConfig to
vfsfile:/C:/projects/jboss5/trunk/build/output/jboss-5.0.0.CR2/server/default/deploy/security/security-jboss-beans.xml
2008-08-07 15:50:16,734 DEBUG
[org.jboss.deployers.structure.spi.helpers.AbstractDeploymentContext]
(main) Added component SecurityConfig to
vfsfile:/C:/projects/jboss5/trunk/build/output/jboss-5.0.0.CR2/server/default/deploy/security/security-jboss-beans.xml
2008-08-07 15:50:16,796 TRACE
[org.jboss.security.auth.login.XMLLoginConfig] (main) Constructing
2008-08-07 15:50:16,828 TRACE
[org.jboss.security.plugins.SecurityConfig] (main) Constructing
Stefan Guilhen wrote:
My guess is that for some reason the SecurityConfig bean is failing
to
register the XMLLoginConfigImpl as the Configuration instance to be used
by the JAAS login process. The stack trace shows that the default
com.sun.security.auth.login.ConfigFile is being used instead.