[OAUTH-WG] Implicit vs. Code flow for Native clients

2012-06-08 Thread Lewis Adam-CAL022
Hi all, I'm looking for a better understanding of why the code flow is recommended as the preferred OAuth flow, even when used for native (public) clients. I totally get why it is preferred for confidential clients, as explained in section 1.3.1. of the version 26 of the draft. The first

[OAUTH-WG] Looking for samples

2012-06-08 Thread José Pavelek
Hi all, I hope this mailing list can be used for this… I’m new in oAuth, I’m a developer trying to use oAuth 2.0 to access google calendar from web access, I use asp.net with VB, my customer want to migrate some private calendar to google calendar, the application is in an intranet, and

[OAUTH-WG] OAuth Core -27 Published

2012-06-08 Thread Mike Jones
The chairs approved publication of OAuth Core draft -27 today. This version is based upon the proposed changes that I'd circulated to the working group. Changes are: *Adds character set restrictions for error, error_description, and error_uri parameters consistent with the OAuth

Re: [OAUTH-WG] OAuth Core -27 Published

2012-06-08 Thread Dick Hardt
On Jun 8, 2012, at 10:51 AM, Mike Jones wrote: The chairs approved publication of OAuth Core draft -27 today. This version is based upon the proposed changes that I’d circulated to the working group. Changes are: ·Adds character set restrictions for error, error_description, and

Re: [OAUTH-WG] OAuth Core -27 Published

2012-06-08 Thread Mike Jones
Apologies, Dick HARDT! :-) From: Dick Hardt [mailto:dick.ha...@gmail.com] Sent: Friday, June 08, 2012 11:09 AM To: Mike Jones Cc: oauth@ietf.org Subject: Re: [OAUTH-WG] OAuth Core -27 Published On Jun 8, 2012, at 10:51 AM, Mike Jones wrote: The chairs approved publication of OAuth Core draft

[OAUTH-WG] I-D Action: draft-ietf-oauth-v2-bearer-20.txt

2012-06-08 Thread internet-drafts
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Web Authorization Protocol Working Group of the IETF. Title : The OAuth 2.0 Authorization Framework: Bearer Token Usage Author(s) : Michael B. Jones

[OAUTH-WG] OAuth 2.0 Bearer Token Specification Draft -20

2012-06-08 Thread Mike Jones
Draft 20 of the OAuth 2.0 Bearer Token Specification has been published. I believe that this draft addresses all DISCUSS issues and comments raised for this specification in IESG review. No normative changes were made, other than specifying the use of Cache-Control options when using the URI

Re: [OAUTH-WG] Cache-Control headers for Bearer URI Query Parameter method

2012-06-08 Thread Mike Jones
Hi Amos, The OAuth Bearer specification now includes the Cache-Control language we'd discussed. See the fifth paragraph of http://tools.ietf.org/html/draft-ietf-oauth-v2-bearer-20#section-2.3. Thanks again,

[OAUTH-WG] Authorization Request via back channel / direct communication?

2012-06-08 Thread Lewis Adam-CAL022
Hi, I have a historical question around front channel / back channel (direct) communications and Authorization Requests. Both the code-flow and implicit-flow utilize a front channel communication through the UA. This makes sense for the delegated credentials case (e.g. shutterfly accessing

Re: [OAUTH-WG] Authorization Request via back channel / direct communication?

2012-06-08 Thread Richer, Justin P.
You're right in that OAuth is optimized for the confidential clients case -- specifically, a client being a web server talking to another web server. But what you've just described, in a nutshell, is the assertion grant type: http://tools.ietf.org/html/draft-ietf-oauth-assertions-03 Which has

Re: [OAUTH-WG] Error Encoding: Conclusion

2012-06-08 Thread Eran Hammer
The new text published today for section 7.2 isn't acceptable. It seems (the lanaguage is unclear when it comes to its actual requirements) to indicate that any protocol used for OAuth token authentication using an error parameter named error must use the new registry. Any authentication method

Re: [OAUTH-WG] Authorization Request via back channel / direct communication?

2012-06-08 Thread John Bradley
To some extent it goes to the question of who do you trust. Most of OAuth is predicated on not sharing the users credential with the client, because clients are not trusted. Your situation may be different if you control the device. If you are using multi factor authentication then using an

Re: [OAUTH-WG] New draft process / editor role

2012-06-08 Thread Anthony Nadalin
Why rant here, talk to the chairs or AD Sent from my Windows Phone From: Eran Hammer Sent: 6/8/2012 6:58 PM To: oauth@ietf.org WG (oauth@ietf.org) Subject: [OAUTH-WG] New draft process / editor role Today, a new draft of the OAuth 2.0 specification was published.

Re: [OAUTH-WG] New draft process / editor role

2012-06-08 Thread William Mills
+1 From: Anthony Nadalin tony...@microsoft.com To: Eran Hammer e...@hueniverse.com; oauth@ietf.org WG (oauth@ietf.org) oauth@ietf.org Sent: Friday, June 8, 2012 7:18 PM Subject: Re: [OAUTH-WG] New draft process / editor role Why rant here, talk to the

Re: [OAUTH-WG] New draft process / editor role

2012-06-08 Thread Franklin Tse
I think the chairs should clarify and explain, via this mailing list, 1. Whether they have authorized Mike Jones and Dick Hardt to author and publish the draft 2a. If they have given the authorization, why they needed to do so and why the editor was not notified; 2b. Otherwise, whether the