Dick,
I may have misinterpreted you design objective of "allowing existing systems to
use existing tokens" as meaning: the refresh_token field shouldn't be defined
as a URI as some existing tokens are too big to fit in URIs.
If the size of existing tokens is an issue then the user-agent flow wi
On 5/18/10 2:42 PM, Dan Brickley wrote:
> On Tue, May 18, 2010 at 10:01 PM, Eran Hammer-Lahav
> wrote:
>> We will be having an interim OAuth meeting at Yahoo! (Sunnyvale, CA) on
>> Thursday 5/20 9am-4pm.
>>
>> I need to know if you plan to attend by EOD today. Please reply just to me
>> to reduce
On Tue, May 18, 2010 at 10:01 PM, Eran Hammer-Lahav wrote:
> We will be having an interim OAuth meeting at Yahoo! (Sunnyvale, CA) on
> Thursday 5/20 9am-4pm.
>
> I need to know if you plan to attend by EOD today. Please reply just to me
> to reduce list spam.
Is there a calendar of upcoming meeti
Hi!
I am in the middle of implementing both the client and server side and noted
some things.
Tried to check a while back to see that the issues was not raised earlier but
if I happen to raise a sensitive issue discussed earlier, let me know.
First two minor comments on the spec.
Page 30 code p
We will be having an interim OAuth meeting at Yahoo! (Sunnyvale, CA) on
Thursday 5/20 9am-4pm.
I need to know if you plan to attend by EOD today. Please reply just to me
to reduce list spam.
EHL
___
OAuth mailing list
OAuth@ietf.org
https://www.ietf.or
On Mon, May 17, 2010 at 8:53 AM, Marius Scurtescu wrote:
> On Mon, May 17, 2010 at 8:29 AM, Evan Gilbert wrote:
> > I'd like to get a standard for redirect URI matching, but think this may
> not
> > be feasible - we are leaving the callback URI registration mechanism
> > undefined and I've heard
