--You received this message because you are subscribed to the Google Groups "OAuth WRAP WG" group.
To post to this group, send email to oauth-...@googlegroups.com.
To unsubscribe from this group, send email to oauth-wrap-w...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/oauth-wrap-wg?hl=en.
<OAuth WRAP Offline Profile.pdf>
Hi EvanThanks for writing this up.It looks the same to me as 5.1 except for the addition of the wrap_username parameter. Is that correct?Given that, it would seem that this could be an "extension" of 5.1, that could also include standardizing the value of wrap_scope. Thoughts?
-- Dickbtw: wrap_name and wrap_password were chosen in 5.1 instead of wrap_client_id and wrap_client_secret to clearly indicate the difference between autonomous profiles and user delegation profiles.
On Thu, Dec 31, 2009 at 12:17 PM, Dick Hardt <Dick....@microsoft.com> wrote:
btw: wrap_name and wrap_password were chosen in 5.1 instead of wrap_client_id and wrap_client_secret to clearly indicate the difference between autonomous profiles and user delegation profiles.wrap_name/wrap_password was a big confusing to me - I thought it was a user name and user password when I first read the section. Also, this proposed extension would further blur the difference between 5.1 and the other profiles.Would it make sense to switch to wrap_client_id & wrap_client_secret for 5.1?