[jboss-dev] missing security config file?

[Adrian Brock]

On Thu, 2008-08-07 at 13:23 -0300, Stefan Guilhen wrote:
> Both SecurityConfig and XMLLoginConfig were old mbeans that have been 
> configured as mc beans while still inheriting ServiceMBeanSupport (so 
> that they could be configured both as mbeans and as mc beans).
> 

What was the real problem? Why does "extends ServiceMBeanSupport"
cause things to stop working?

Since this was working before, it sounds to me like
there has been some other bug introduced in the latest MC.

> I've removed the ServiceMBeanSupport inheritance from the beans and 
> removed the ServiceMBean inheritance from their interfaces as well and 
> now both beans start correctly (also had to add start and stop methods 
> to replace startService and stopService). So now those beans can only be 
> configured as mc beans and use the @JMX annotation to export their 
> "MBean view".
> 
> My question is whether inheriting ServiceMBeanSupport is now considered 
> wrong for a mc bean or not. 

It's not wrong, but it is cruft.

> If it is, and beans are only supposed to be 
> configured as mc beans, then I'll commit the changes I've made to be in 
> line with Ales/Adrian's changes.
>
> Ales Justin wrote:
> > 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.
> > _______________________________________________
> > jboss-development mailing list
> > jboss-development at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/jboss-development
> 
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development
-- 
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx