Cool, thanks - Henry
On Fri, Jun 15, 2012 at 10:22 AM, Ryan J Baxter <rjbax...@us.ibm.com> wrote: > The change was already rolled back, I did that yesterday. Doug is just > talking about the new patch. I was talking to Doug on GChat and I think > the reason he is running into problems is because he is testing in the > common container with secure tokens enabled but the common container has a > hard coded insecure token in it. He is going to do some more testing in > his own container later on. > > -Ryan > > > > > From: Henry Saputra <henry.sapu...@gmail.com> > To: daviesd <davi...@oclc.org>, > Cc: dev@shindig.apache.org > Date: 06/15/2012 01:07 PM > Subject: Re: Pass token on listMethods to enable > allowUnauthenticated=false (issue 6306074) > > > > Ryan, > > I think we need to rollback the change for now until we got the right fix. > > - Henry > > On Fri, Jun 15, 2012 at 9:34 AM, daviesd <davi...@oclc.org> wrote: >> I am still having issues. >> >> I rebuilt everything with secure tokens enabled, but skipped tests so > that >> the build would complete. Now the listMethods call succeeds, but then > the >> metadata call fails with org.apache.shindig.auth.SecurityTokenException: >> Invalid security token john.doe:john.doe:appid:cont:url:0:default. >> >> This is with the 2 file patch you sent and shindig.properties >> allowUnauthenticated=false and secure tokens set in container.js. I am >> hitting the commoncontainer and trying to render horoscope. >> >> I'm off for the rest of the day. I'll check back on things on Monday. >> >> Doug >> >> > >
