So, to iterate over the possibilities:
a) oauth_callback_confirmed not sent (regardless of whether
oauth_callback was specified by consumer or not) -> 1.0
b) oauth_callback_confirmed == false -> 1.0a (and this in particular
would indicate an error condition for the consumer)
c) oauth_callback_confirmed == true -> 1.0a (all systems go)
Is that the right way to interpret the version behaviour? Thanks
On May 14, 10:04 pm, Brian Eaton <bea...@google.com> wrote:
> On Thu, May 14, 2009 at 2:45 AM, Jack <tjerk.meest...@gmail.com> wrote:
> > 1) How would the consumer know what spec is used on the service
> > provider? i.e. should it throw an exception if the
> > oauth_callback_confirmed is missing or set to anything but "true" ?
>
> If the SP does not return oauth_callback_confirmed=true, the consumers
> knows the SP does not support 1.0a. It's up to the consumer to decide
> what to do at that point.
>
> > 2) Also, in the example where there's no callback ("oob"), will the
> > service provider still return "true" for the oauth_callback_confirmed
> > parameter?
>
> A consumer that wants to use OAuth 1.0a always passes oauth_callback
> on the request token step, and the SP always responds with the
> confirmation.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"OAuth" group.
To post to this group, send email to oauth@googlegroups.com
To unsubscribe from this group, send email to oauth+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/oauth?hl=en
-~----------~----~----~----~------~----~------~--~---
