I was using a development snapshot. I downloaded and tried it in version
1.4. It works. Thanks.
-PC

On Wed, Aug 15, 2012 at 5:26 AM, Hiram Chirino <hi...@hiramchirino.com>wrote:

> I just tried it out with Apollo 1.4 and it seems to work:
>
> Opening Web Socket...
> Web Socket Opened...
> >>> CONNECT
> login:guest
> passcode:guest123
>
>
> <<< CONNECTED
> version:1.0
> server:apache-apollo/1.4
> host-id:apollo
> session:apollo-3
> heart-beat:100,10000
> user-id:guest
>
>
> In terms of configuration I just added 'guest=guest123' to the
> users.properties file and then updated the groups.properties file with
> 'admins=admin|guest'.
>
> Could you give us more details on what version and config your using?
>
> On Tue, Aug 14, 2012 at 5:29 PM, Paddy Carman <paddy.car...@gmail.com
> >wrote:
>
> > Hi -
> >     I added a new user/password called guest/guest123 in users.properties
> > file. I'm able to login to the broker using a PHP client (with
> > guest/guest123). But when I use a websocket client (using the chat
> example
> > from https://github.com/jmesnil/stomp-websocket/tree/master/example/chat
> ),
> > it gives me the following error. I have tried with Firefox, and Chrome. I
> > do not have a problem when I use admin/password. What am I doing wrong?
> The
> > error message is given below.
> > -PC
> >
> > Opening Web Socket...
> > Web Socket Opened...
> > >>> CONNECT
> > login:guest
> > passcode:guest123
> >
> > <<< ERROR
> > message:Not authorized to connect to virtual host 'apollo'.
> > Principals=[org.apache.activemq.jaas.UserPrincipal(guest),
> >
> >
> org.apache.activemq.apollo.broker.security.SourceAddressPrincipal(0:0:0:0:0:0:0:1)]
> >
> >
> >
> > Whoops! Lost connection to ws://localhost:61623/stomp
> >
>
>
>
> --
>
> **
>
> *Hiram Chirino*
>
> *Software Fellow | FuseSource Corp.*
>
> *chir...@fusesource.com | fusesource.com*
>
> *skype: hiramchirino | twitter: @hiramchirino<
> http://twitter.com/hiramchirino>
> *
>
> *blog: Hiram Chirino's Bit Mojo <http://hiramchirino.com/blog/>*
>
> *
> *
>
> *
> *
>

Reply via email to