Client JMS does not use JAAS.
It is a TODO in the spec for a future version.
The JMS Resource Adapter deployed within JBoss will use JAAS
because it is wrapped with a JCA connection manager that understands it.
The only portable solution is to write your own JMS wrapper that understands
JAAS
and
I have this exact same problem.
Rich client authenticating via JAAS ClientLoginModule to JBoss EJB server.
This works fine. However the same JAAS authentication is ignored for opening
connection to a JMS topic or queue and I have to manually supply the username
and password in the call to ope
Still cannot get this to work. Currently my client application is logging in twice,
once using JAAS for the ejb access and once when creating the topic connection.
I cannot work out how to unify the security for JMS and EJBs when using both from an
external client.
thanks,
brian wallis...
Vie
Thanks for the reply. But I think my initial question might have been a little
misleading.
It is the client side that is accessing the beans AND connecting to the JMS topic, I
have something like the following in the client app:
lc = new LoginContext("jbossmq",handler);
lc.login();
// ...
Configure the jms security domain to use the
org.jboss.resource.security.CallerIdentityLoginModule to use the ejb credentials.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3838789#3838789
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=post
