http://anil-identity.blogspot.com/2009/05/as51-specifying-custom-call-back.html
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4231410#4231410
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4231410
Here is the MBean Configuration:
| mbean code=org.jboss.security.plugins.JaasSecurityManagerService
| name=jboss.security:service=JaasSecurityManager
| ...
| attribute
name=CallbackHandlerClassNamecom.george.security.handler.MyCustomCallbackHandler/attribute
|
| /mbean
|
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
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 ??
View the original post :
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 ?
View the original post :
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
