Thanks for the quick reply, James.

Currently, I am using the 3.x branch which means I am using a subclass of
org.activemq.security.SecurityAdapter to make queries agains my SSO gateway.
But my current implementation only supports full username and password
access, not SSO tokens. If I can differentiate which request where password
based and which where SSO tokens, I can make the SecurityAdapter work. What
can I do from the client side to pass this additional information? Any
thoughts?

The only solution that I can think of, and still stay within the JMS spec,
is to append a query string(of some sort) at the end of the connection
string.

As for 4.x, I notice that SecurityAdapter is removed entirely and replaced
with BrokerPlugin approach.
Because of the radical change, I am goto remain using 3.x for now as we are
close to the end of an iteration. 

Rick 
--
View this message in context: 
http://www.nabble.com/ActiveMQ-participating-in-a-SSO-environment-t1344471.html#a3597535
Sent from the ActiveMQ - User forum at Nabble.com.

Reply via email to