+1
Eran, thanks for framing this up...
On Sep 28, 2010, at 12:14 PM, Brian Campbell wrote:
> +1 seems like a pragmatic compromise
>
> On Tue, Sep 28, 2010 at 12:44 PM, Marius Scurtescu
> wrote:
>> On Tue, Sep 28, 2010 at 9:05 AM, George Fletcher wrote:
>>> +1 I think this is a great path forw
D
On Jul 8, 2010, at 9:29 AM, David Recordon wrote:
I'm honestly trying to decide myself and a few other people are in similar
situations. Thus a poll:
A) Yes, I'm going to be in Maastricht
B) Maybe, depends on the number of OAuth WG members going
C) Maybe, depends on some other reason
D) No
If
Thanks Torsten for more of your good thinking and write-up...
At Intuit, using 1.0a, we did an experiment with one of our mobile apps using
multiple tokens. The programming model of having the client maintain a mapping
of token to ROA endpoint, so they used the correct token turned out to be a
For the ignorant (me), how does the spec, now hosted at IETF, move
forward?
Do we still discuss on this list?
Who does the editing work?
Is .txt what we all have to read now?
___
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailm
The amount of writing done on scope the past few weeks indicates this
concept generates a lot of passion. I hope we will spend some time on it
during IIW X and at our 20-May f2f.
For me, delegation is an identity in my system authorizing my system to
issue a toke to an identity, which is not in
With Doug in an all day mtg, we have not sync'd on this...so one of us
may respond again on this topic.
I think I am +1 w/ Brian E.
In the flow from SAML gateway to STS to protected resource, I don't see
caching both an access and refresh token as getting me any efficiency.
Certainly, it adds com
