Am thinking that the fix for
http://issues.apache.org/activemq/browse/AMQ-2335 should just whack the
password. leaking or providing the user in the advisory is probally ok.
When logging connection info commands we just remove or replace with ""
the password.
https://issues.apache.org/jira/brows
Rob,
I'm stuck on something that is probably obvious but I just can't figure out
how to do it.
What I want to do is retrieve the userName from an incoming Stomp
connection. I am creating the broker in my code and have also set up
monitoring Advisory messages. The onMessage function receives t
On 29 Jul 2009, at 16:50, > wrote:
Hi Rob,
Crickey!!!
This is tracked by http://issues.apache.org/activemq/browse/
AMQ-2335 -
I don't think there's a work around without extending an existing
AuthenticationBroker (same package as AuthenticationPlugins) to copy
the ConnectionInfo - remove
Hi Rob,
> Crickey!!!
> This is tracked by http://issues.apache.org/activemq/browse/AMQ-2335 -
> I don't think there's a work around without extending an existing
> AuthenticationBroker (same package as AuthenticationPlugins) to copy
> the ConnectionInfo - remove the username/password from the copy
On 28 Jul 2009, at 22:56, > wrote:
I've been working on setting up an ActiveMQ 5.2 broker and coding
clients for it for the last few weeks, and now I need to be notified
when somebody logs in. I was hoping I could use the topic
ActiveMQ.Advisory.Connection for that, so I set up a consumer on
