Hello everyone,
there is an interresting problem with security domain used to authenticate users connecting to JMS resources. The thing is that, there is custom implementation of authentication module (more constraints required) and a configuration of login-module that references this implementation.
<application-policy name="CustomSecurityDomain">
<authentication>
<login-module code="custom.authentication.LoginModule" flag="required">
</login-module>
</authentication>
</application-policy>
The class custom.authentication.LoginModule sits within EAR. Then this authentication module is configured to be used by JMS authentication:
<bean name="SecurityStore" class="org.jboss.jms.server.jbosssx.JBossASSecurityMetadataStore">
<annotation>@org.jboss.security.integration.password.Password(securityDomain=suckerPassword,methodName=setSuckerPassword)</annotation>
</bean>
With this setup, the authentication always fails and by debugging (I probably have wrong logging levels set) it is known that CustomSecurityDomain is on blacklist. When the custom.authentication.LoginModule is separated into separate jar and deployed on its own, then everything (authentication) work just fine, but then there are different reasons that prevent usage of this setup. Did somebody faced problem like this? Any solution or advice is welcome!
thanks, Martin