Hi James, this JMSXUserID feature is great, however I had a few
problems using it so I have a couple of questions and possible
enhancements for the documentation.
I first tried to use
javax.jms.Message.getStringProperty("JMSXUserID"), but that always
returned null, so I found out that I had to cast the message and use
ActiveMQMessage.getUserId().
Is that the intended usage or should you be able to get it via a
property? If not, can we add something to the JMSXUserID web page that
documents this with an example?
Also, I'll have a patch soon that fixes what looked like a problem
with the userid never getting set in the broker. It's part of a larger
patch which enhances the SSL security Sepand contributed last week.
Thanks,
Kelly
On 6/9/06, James Strachan <[EMAIL PROTECTED]> wrote:
If you enable the populateJMSXUserID flag on the broker then you will
get the authenticated username of the sender set on each message on
the JMSXUserID header on the JMS message.
For more detail see
http://activemq.org/site/jmsxuserid.html
On 6/9/06, ENP <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I use jaasAuthenticationPlugin and authorizationPlugin. Can receiver read
> message sender username?
>
> Sender can add custom header to message with his name but it can add wrong
> name. Can receiver properly identify sender?
> --
> View this message in context:
http://www.nabble.com/Sender-Name-ID-t1760458.html#a4789096
> Sent from the ActiveMQ - User forum at Nabble.com.
>
>
--
James
-------
http://radio.weblogs.com/0112098/
