activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMQ-2995) allowAnonymousAccess doesn't work for websockets
Date Sat, 02 Nov 2013 20:31:17 GMT

     [ https://issues.apache.org/jira/browse/AMQ-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Claus Ibsen updated AMQ-2995:
-----------------------------

    Component/s: Transport

> allowAnonymousAccess doesn't work for websockets
> ------------------------------------------------
>
>                 Key: AMQ-2995
>                 URL: https://issues.apache.org/jira/browse/AMQ-2995
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Transport
>    Affects Versions: 5.4.1, 5.4.2
>            Reporter: Karl Palsson
>            Priority: Minor
>
> Connecting anonymously via plain stomp works just fine with 5.4+, but from websockets,
using jmesnils stomp.js, there's no way to easily send the requisite nulls from javascript.
> I was previously using the patch attached to https://issues.apache.org/activemq/browse/AMQ-2081
also available at http://code.google.com/p/activemq-anonymous-user/
> This allowed me to use {code}client.connect("", "", onconnect, onerror);{code} but with
the built in anonymous access now in a 5.4+, this fails to login with incorrect username/password
> I've tried every other "null" combination I can think of, but given that stomp requires
the login/passcode fields, jmesnil's library is right to demand them, using javascript null
keyword, produces usernames and passwords of null/null which also fails the login.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message