>-----Original Message----- >From: Ciancetta, Jesse E. >Sent: Tuesday, November 08, 2011 10:40 AM >To: [email protected] >Subject: RE: security token (st) parameter is missing > >>-----Original Message----- >>From: Chatree Srichart [mailto:[email protected]] >>Sent: Friday, November 04, 2011 6:39 AM >>To: [email protected] >>Subject: security token (st) parameter is missing >> >>Hi community, >> I am trying to get a pre token login works but it does not. > >I'm not quite sure what you mean here -- are you trying to send a "signed" >makeRequest maybe? > >If that's not what you mean could you please describe what it is your trying to >do in a little more detail? > >> I think the >>security token (st) parameter always missing causes the problem. Could you >>please tell me how to fix it? I would like to sent the "st" parameter >>whenever I call a makeRequest function. > >I believe the ST only gets sent back to shindig on makeRequest when doing >signed requests. Here is an example that triggers the ST to be sent: > >-- > >var url = "http://www.example.com";; >var params = {}; >params[gadgets.io.RequestParameters.AUTHORIZATION] = >gadgets.io.AuthorizationType.SIGNED; > >gadgets.io.makeRequest(url, function (response) { > console.dir(response); >}, params); > >-- > >I haven't tried that with Rave though so I'm not sure if it will work or not >-- I'll >try it in a bit and report back. It may give an error because I think you >need to >add some configuration on the shindig side to tell shindig how to sign the >requests before it sends them out.
I tried this out in an out of the box Rave environment and as I suspected it does indeed result in an error on the shindig side. In order for signed fetch to work you will need to configure the "Outbound OAuth support" settings in the shindig.properties file. If you need any help in that area the shindig dev list is probably the best place to ask questions. >>Regards, >>Chatree Srichart
