Hi Michael, sorry for the delay, I got sick last few days. The tip helped, thank you!!!
I have a patch which stubs out a dummy test token for /content/samplecontainer/examples/commoncontainer. This container is currently broken due to invalid security token. I'll submit this patch and will check code in soon if no objection. Han From: Michael Hermanto <[email protected]> To: [email protected] Date: 02/03/2011 02:09 PM Subject: Re: RES: security token (in the new common container) The security token minted in the iframe URL returned via /api/rpc comes DefaultIframeUriManager.generateSecurityToken(). You can supply your own SecurityTokenCodec or override generateSecurityToken() to yield the token that you want. Hope that helps. On Thu, Feb 3, 2011 at 6:09 AM, Han Nguyen <[email protected]> wrote: > hmmm, it doesn't seem to be set for service api path /rpc. What do I > missed? > I also see some new code in trunk setting the security token in a request > header for OAuth2 option for the old shindig.container. Does the new > common container support this yet? > Help please! > Han > > > > From: "Xandeco, Maxwell" <[email protected]> > To: "[email protected]" <[email protected]> > Date: 02/03/2011 06:42 AM > Subject: RES: security token > > > > > > shindig.auth.updateSecurityToken('john.doe:john.doe:appid:cont:url:0:default'); > > cheers. > ________________________________________ > De: Han Nguyen [[email protected]] > Enviado: quinta-feira, 3 de fevereiro de 2011 2:48 > Para: [email protected]; [email protected] > Assunto: security token > > Hi, > How do I set the security token using the new common container? > Thank you, > Han >
