I think you'll have to put the oauth_consumer_key in the gadget XML.

I'd think otherwise if Netflix started accepting RSA keys from
opensocial containers, but I think they only use keys they issued
themselves.

On Thu, Apr 2, 2009 at 5:23 PM, Viji Subramanian
<[email protected]> wrote:
> I could hardcode the oauth_consumer_key in the gadget xml, but then the
> gadget won't be write once and run in any container..
>
>
>
> Viji Subramanian wrote:
>>
>> Brian,
>>
>> Per oauth spec, oauth_token and oauth_callback - both Optional and any
>> additional parameters as defined by the Service Provider can be added to the
>> authorization url.
>>
>> I am developing a netflix gadget - and per their API,  I need to send the
>> following in Netflix user authorization URL:
>> |https:api-user.netflix.com/oauth/login|
>>
>>   * |oauth_consumer_key| - Consumer application's key
>>   * |oauth_token| - The request token that was obtained in the
>>     previous step. Netflix may declare that this parameter is required
>>     or may accept requests to the user authorization URL without the
>>     request token, in which case the user is prompted to enter the
>>     authorization manually.
>>   * |application_name| - The name of your application
>>   * |oauth_callback| - (Optional) You can specify a URL for Netflix to
>>     redirect the user back to the consumer as part of obtaining user
>>     authorization. The request token must be appended to
>>     |oauth_callback| when you redirect back to the callback.
>>
>> Currently, the shindig (0.8) code - buildAznUrl (Oauthfetcher.java) adds
>> oauth_token ONLY to authorization Url,
>>
>> I am able to specify application_name and oauth_callback.. However,
>> without modifying shindig code, i don't see a way of adding
>> oauth_consumer_key to the authorization url.
>>
>> 1) I wanted to know if there is plan to accomodate extra parameters ?
>> 2) I remember reading earlier on that there might be changes to the oauth
>> Section in gadget xml.  Can you point me to some references as to what the
>> status  is on that as well ?
>>
>> Thanks
>>
>>
>
>

Reply via email to