On 20 October 2010 14:29, cearl <[email protected]> wrote: > Hi, > I'm not quite sure how to handle authentication in the wiab either. > I've been using an older distribution for development, and just today > tried running the new release. > Here's what I note: > 1. When I click "Register", I enter a user name and password. Even for > new accounts, I the response > "Account already exists" > Console debug log states: > "RESPONSE /auth/register 403 > EOF: org.eclipse.jetty.io.EofException" > > Am I setting up jaas (or some other authentication module?) correctly? > The only things I changed are the various host names in run-config.sh > and these settings ran with distributions up to Oct 8. >
The default auth module is currently a fake. You don't need to register accounts, just log in with any address and an empty password. > 2. When I attempt to login, the response is > HTTP ERROR: 403 > Problem accessing /auth/signin. Reason: Forbidden > (the location is localhost:9898/auth/signin?r=/ ) > > 3. I would think first that the account username + password correspond > to XMPP (ejabberd in my case) user, password, domain. I tried logging > in with valid XMPP usernames & passwords for my XMPP @localhost > domain, but does not seem to work. > Client auth is not related to XMPP at all, although for some cases it would be nice to hook up client auth to an XMPP system. But it's not implemented that way yet. Let me know if there are other details needed to troubleshoot this. > Hopefully, its something trivial that I goofed on. > Thanks. Looks like tremendous strides. > Also, is there a way of limiting permutations done in the compilation? > or are there at least provisions now handing permutations off to > multiple cores/threads? > We're working on that right now. Stay tuned to the list. A. > Thanks again. > > On Oct 19, 6:03 pm, Joseph Gentle <[email protected]> wrote: > > Thats weird. And I don't know why you have quotes in your domain name. > > Can you try removing / moving away your run-config.sh and then run > > ./run-server.sh ? > > > > (That'll use the run-nofed-config.sh settings, which have more sane > defaults.) > > > > -J > > > > > > > > On Wed, Oct 20, 2010 at 3:40 AM, DanielS <[email protected]> wrote: > > > Thanks Joeseph Gentle, that was it - I hadn't compiled it...I think I > > > missed the underscore and overlooked the BUILD failed message. > > > > > Still have a problem when I try to create a wave: > > > > > Tue Oct 19 19:33:35 GMT+300 2010[INFO] Attemping to reconnect > > > Tue Oct 19 19:35:48 GMT+300 2010[INFO] WaveCreationEvent received > > > Tue Oct 19 19:35:48 GMT+300 2010[INFO] Not creating wave since there > > > is no backend > > > > > I logged in without providing any details so my username is just > > > @'hostname'. I can login as anything I want so long as I don't provide > > > a password. > > > > > I still can't seem toregister(You can only create users at the > > > 'hostname' domain) and I haven't added the @domain part (it seems > > > outside the field anyway). > > > > > On 19 oct., 01:35, Joseph Gentle <[email protected]> wrote: > > >> You need to run > > >> % ant compile_gwt > > >> as well, to compile the web client. > > > > >> When youregistera user, leave out the @domain part and it'll be > > >> added automatically. > > > > >> -J > > > > >> On Mon, Oct 18, 2010 at 7:45 PM, DanielS <[email protected]> wrote: > > >> > Hi all, > > > > >> > Does it do anything yet? Does anyone have any screenshots of what I > > >> > should be seeing for the web client? > > > > >> > I tried running the wave server and localhost:9898 loaded just fine > (I > > >> > can see the wave logo top left and login /registerlinks top > > >> > right)...but other than that it doesn't seem to have any > > >> > functionality... > > > > >> > I also get an error when I try toregister: " Can only create user on > > >> > domain 'hostname' " > > > > >> > Cheers, > > > > >> > Dan > > > > >> > -- > > >> > You received this message because you are subscribed to the Google > Groups "Wave Protocol" group. > > >> > To post to this group, send email to [email protected] > . > > >> > To unsubscribe from this group, send email to > [email protected]<wave-protocol%[email protected]> > . > > >> > For more options, visit this group athttp:// > groups.google.com/group/wave-protocol?hl=en. > > > > > -- > > > You received this message because you are subscribed to the Google > Groups "Wave Protocol" group. > > > To post to this group, send email to [email protected]. > > > To unsubscribe from this group, send email to > [email protected]<wave-protocol%[email protected]> > . > > > For more options, visit this group athttp:// > groups.google.com/group/wave-protocol?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Wave Protocol" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<wave-protocol%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/wave-protocol?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Wave Protocol" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en.
