- "PieterN" <[EMAIL PROTECTED]> wrote:
> Patch:
> ---
> ../../../activemq-snapshot/src/activemq-core/src/main/java/org/apache/activemq/transport/stomp/ProtocolConverter.java
>
...
I've tried this patch, and it doesn't change anything. Stomp clients can
still connect with any userna
Tom Samplonius-2 wrote:
>
> Actually, it appears that the username and password are ignored. I
> fought with JAAS for about four hours before decided to try to read the
> code, and the comments say that the password is ignored. There appears to
> be no way to get a config that doesn't
> che
I've added some documentation about the webconsole and I included a
section about how to password protect it (although only on jetty, but
I hope the folks will figure out how to 'translate'' that to tomcat by
themself :).
And for the JMX-password issue there is a patch by Andrew Deason
(https://is
- "James Strachan" <[EMAIL PROTECTED]> wrote:
> On 6/2/07, Tom Samplonius <[EMAIL PROTECTED]> wrote:
> >
> > How much more work needs to occur to get Stomp protocol support to
> a usable state?
>
> Huh? :) Its very useable right now
James,
Another component of getting Stomp to a usable
- "James Strachan" <[EMAIL PROTECTED]> wrote:
> On 6/2/07, Tom Samplonius <[EMAIL PROTECTED]> wrote:
> >
> > How much more work needs to occur to get Stomp protocol support to
> a usable state?
>
> Huh? :) Its very useable right now
>
>
> > The biggest issue is lack of any authentication
On 6/2/07, Tom Samplonius <[EMAIL PROTECTED]> wrote:
How much more work needs to occur to get Stomp protocol support to a usable
state?
Huh? :) Its very useable right now
The biggest issue is lack of any authentication support for Stomp, so anyone
with access to the Stomp port can get a
- "Tom Samplonius" <[EMAIL PROTECTED]> wrote:
> The Web Console has similar issues. There is no easy way to
> password protect it. But if you password protect JMX access, it will
> break the Web Console.
...
I was wrong here. I based my comment on this bug report:
http://www.nabble.c
