OK - will do.
From: Eran Hammer
Sent: 6/16/2012 12:43 PM
To: Mike Jones; oauth@ietf.org WG (oauth@ietf.org)
Subject: RE: [OAUTH-WG] Section 7.2
I would rather these restrictions be in the error registry section below and
add a forward reference from 7.2.
EH
Fro
I would rather these restrictions be in the error registry section below and
add a forward reference from 7.2.
EH
From: Mike Jones [mailto:michael.jo...@microsoft.com]
Sent: Saturday, June 16, 2012 12:17 PM
To: Eran Hammer; oauth@ietf.org WG (oauth@ietf.org)
Subject: RE: [OAUTH-WG] Section 7.2
While adding the new text into a proposed draft, I realized that no character
set restrictions on the error code values were defined in the agreed text.
Therefore, I've added the following sentence (which was already present in -27):
Values for these error codes MUST NOT include
Nov demonstrated the problem to us at Yapp and we used solution 4 (because the
solution is server side and our app was in the app store).
FB Connect is authentication and authorization, where OAuth 2 is concerned only
with authorization – I'm not sure that app developers appreciate this subtlety
