These posts of Yaron's outline the basic vision and flows:
http://www.goland.org/adhocauthentication/
http://www.goland.org/oauthgenericdelegation/
We hope to also come out with a description in Internet-draft style soon to
provide concrete details about possible implementation choices for this kind of
end-to-end scenario. But if you dig into these posts, I believe you'll find
there's a lot there already at the conceptual level.
-- Mike
From: Dick Hardt [mailto:[email protected]]
Sent: Tuesday, October 26, 2010 9:38 PM
To: Mike Jones
Cc: [email protected]; [email protected]
Subject: Re: Simple Web Discovery
On 2010-10-26, at 4:33 PM, Mike Jones wrote:
Having a simple discovery method for services and resources is key to enabling
many Internet scenarios that require interactions among parties that do not
have pre-established relationships. For instance, if Joe, with e-mail address
[email protected]<mailto:[email protected]>, wants to share his calendar with
Mary, then Mary's calendar service, in the general case, will need to discover
the location of Joe's calendar service. For example, Mary's calendar service
might discover that Joe's calendar service is located at
http://calendars.proseware.com/calendar/joseph by doing discovery for a service
named urn:adatum.com:calendar at example.com<http://example.com> for the
account joe.
I think it would be really useful to complete the scenario. What happens when
Mary's service discovers Joe's calendar service? How does Joe give Mary's
calendar service permission to access his calendar? How does Joe identify Mary?
-- Dick
_______________________________________________
OAuth mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/oauth
