Shindig does not store consumer key for gadgets by default so we need to override the default SHindig OAuth store for it.
Doug, I assume you have your own OAuth store/provider for your OAuth flow? - Henry On Fri, Apr 27, 2012 at 8:20 AM, daviesd <[email protected]> wrote: > Here's the logic in View.java > > if (needViewer && (!this.signViewer || this.authType == AuthType.NONE)) > { > throw new SpecParserException("Must sign by viewer to request > viewer."); > } > > needsViewer is set IF data-pipelining has a userId of @viewer which > > <os:ViewerRequest key="viewer"/> > > Would be requiring. > > So this tells me that any data-pipelining that deals with viewer needs to be > signed (or I'm missing something). > > If that's true, then I'm stumped on the 403 error I get back when I enable > signing, because then it appears from the consumer key error that I need to > have oauth enabled. > > doug > > > On 4/26/12 6:35 PM, "Ryan J Baxter" <[email protected]> wrote: > >> Doug, I have not tried this in a while, but last time I did OAuth was not >> required. >> >> -Ryan >> >> >> >> >> From: daviesd <[email protected]> >> To: shindig <[email protected]>, >> Date: 04/26/2012 06:13 PM >> Subject: Does data-pipelining in proxied content require oauth to >> be configured? >> >> >> >> I have a developer trying to use proxied content. Their gadget looks as >> follows: >> >> <Content >> href="http://localhost/some.php"; >> type="html" >> authz="signed" >> xmlns:os="http://ns.opensocial.org/2008/markup";> >> <os:ViewerRequest key="viewer" /> >> </Content> >> >> We keep getting a 403 back from the server >> >> WARNING: The following fatal error occurred when OAuth was fetching >> content: >> Unable to retrieve consumer key. >> Apr 26, 2012 6:04:38 PM org.apache.shindig.gadgets.render.Renderer render >> INFO: The gadget at http://dl.dropbox.com/u/xxxxx/gadgets/karen_proxy.xml >> did not render. The following error occurred: Unable to reach remote host. >> HTTP status 403. >> >> If we set authz to none then we get ³Must sign by viewer to request >> viewer². >> >> So I¹m assuming you must turn authz on for data-pipelining to work. Does >> this mean I need to configure oauth in shindig.properties? I don¹t >> currently and this is probably my problem, but just checking. >> >> doug >> >> > >
