Friends..
I have a JMS topic, protected for read and write operation to a specific a role. I am using ClientLoginModule in auth.conf file for the client to be able to properly propogate the user and pass to the server. But its not reaching upto the server and server is taking the default unauthenticated user "none". See trace enabled server log here...
2004-12-13 19:08:09,732 TRACE [org.jboss.mq.server.TracingInterceptor] CALLED : authenticate
2004-12-13 19:08:09,732 TRACE [org.jboss.mq.security.ServerSecurityInterceptor] Autenticating user null/null
2004-12-13 19:08:09,742 TRACE [org.jboss.security.auth.login.XMLLoginConfigImpl] Begin getAppConfigurationEntry(jbossmq), size=10
2004-12-13 19:08:09,746 TRACE [org.jboss.security.auth.login.XMLLoginConfigImpl] End getAppConfigurationEntry(jbossmq), authInfo=AppConfigurationEntry[]:
[0]
LoginModule Class: org.jboss.mq.sm.file.DynamicLoginModule
ControlFlag: LoginModuleControlFlag: required
Options:name=sm.objectname, value=jboss.mq:service=StateManager
name=unauthenticatedIdentity, value=none
2004-12-13 19:08:09,771 TRACE [org.jboss.mq.sm.file.DynamicLoginModule] initialize
2004-12-13 19:08:09,771 TRACE [org.jboss.mq.sm.file.DynamicLoginModule] Saw unauthenticatedIdentity=none
2004-12-13 19:08:09,773 TRACE [org.jboss.mq.sm.file.DynamicLoginModule] login
2004-12-13 19:08:09,793 TRACE [org.jboss.mq.sm.file.DynamicLoginModule] Authenticating as unauthenticatedIdentity=none
2004-12-13 19:08:09,793 TRACE [org.jboss.mq.sm.file.DynamicLoginModule] User 'none' authenticated, loginOk=true
2004-12-13 19:08:09,794 TRACE [org.jboss.mq.sm.file.DynamicLoginModule] commit, loginOk=true
Lately I read in the documentation that ClientLoginModule binds the username and password to the JBoss EJB invocation layer for later authentication on the server. If its true, then, can somebody may please advise on what LoginModule to use for JMS invocation layer ?
Thanks,
Shiva