CallbackHandlerClassName not being used !

[gastaldi]

Hello !!

I am using JBoss 5.0.1GA, and have customized my own Security CallbackHandler to handle custom callbacks. As of JBoss 4.2.3, I created a new CallbackHandler, and registered into the following MBean


...
com.george.security.handler.MyCustomCallbackHandler



However, this configuration has no effect. The CallbackHandler received by my modules is always a org.jboss.security.auth.callback.JBossCallbackHandler.

This used to work on versions pre-5.0 (Tested against 4.2.3.GA).

How do I make it work on 5.0.0+ ?

[gastaldi]

Here is the MBean Configuration:

 <mbean code="org.jboss.security.plugins.JaasSecurityManagerService"
 name="jboss.security:service=JaasSecurityManager">
...
 <attribute name="CallbackHandlerClassName">com.george.security.handler.MyCustomCallbackHandler</attribute>

</mbean>

[anil.saldhana]

deploy/security/security-jboss-beans.xml

<!-- JNDI Based Security Management -->
<bean name="JNDIBasedSecurityManagement"
 class="org.jboss.security.integration.JNDIBasedSecurityManagement"/>

You will have to create an instance of your call back handler and then inject into this bean.

<bean name="myhandler" class="com.george....." />

<!-- JNDI Based Security Management -->
<bean name="JNDIBasedSecurityManagement"
 class="org.jboss.security.integration.JNDIBasedSecurityManagement">
 <property name="callBackHandler"><inject bean="myhandler"/>
</bean>

[gastaldi]

Anil,

I´ve already done that, and the callbackHandler is set, BUT, somehow, the class is instantiated again (ignoring the XML configuration) and the default callback is used again.

Any more suggestions ??

[gastaldi]

It seems that there is a bug in org.jboss.security.integration.SecurityDomainObjectFactory.

It always creates a new JNDIBasedSecurityManagement, no matter how I configured it.

Maybe changing that will fix this issue ?

[anil.saldhana]

"gastaldi" wrote:
It seems that there is a bug in org.jboss.security.integration.SecurityDomainObjectFactory.

It always creates a new JNDIBasedSecurityManagement, no matter how I configured it.

Maybe changing that will fix this issue ?

Looking at it, I can see that there are issues.

Let me think about workarounds and get back. We want to get this fixed for AS5.1

[anil.saldhana]

http://anil-identity.blogspot.com/2009/05/as51-specifying-custom-call-back.html