Hi Anthony, Firefox has been doing some pioneering work in this respect. Take a look at the Firefox Account Manager[1] for a sketch of what they're trying to do.
The initial work is exciting, but I think there's general agreement that there's a huge opportunity for browsers to become rich entry points to the web for users, along the lines of what Flock was trying to do at the start of the Web 2.0 kick. But with more "future." :-) b. [1] http://www.mozilla.com/en-US/firefox/accountmanager/ On 19 May 2010 14:01, Anthony Nadalin <[email protected]> wrote: > Why does this have to involve the browser vendors > > > > From: [email protected] > [mailto:[email protected]] On Behalf Of Santosh Rajan > Sent: Wednesday, May 19, 2010 1:12 AM > To: David Recordon > Cc: Martin Atkins; [email protected]; Blaine Cook > Subject: Re: Connect spec updated > > > > HA! BullShit! > > > > You know what?. I am beginning to believe that we need get the browser > vendors to the OpenID community. Yes Google and Microsoft are already here, > but i don't think they are here in the capacity of "browser vendors". We > also need the mozilla, opera, safari guys. > > > > And Mozilla has really been doing some good work in this area. Here is a > link. > > https://wiki.mozilla.org/Labs/Weave/Identity/Account_Manager/Spec/Latest > > > > > > On Wed, May 19, 2010 at 1:25 PM, David Recordon <[email protected]> wrote: > > Coming out of some conversations at IIW today I've made some changes to the > proposal. Patch is attached, but they are: > > - Allow passing in `user_id` as a hint when not using immediate mode in the > request. > > - Continue to allow users to enter URLs, email addresses, and click buttons > but the returned user identifier must be a HTTPS URI. > > - Include the expiration time within the signature. > > - Clarify how you verify if the token endpoint is authoritative for a given > user identifier. > > - Simplify discovery by removing LRDD and using host-meta to determine the > server token endpoint on a per domain (or sub-domain) basis. We're having a > hard time finding use cases of running multiple different OpenID servers per > domain. > > - Remove the separate user info API endpoint and instead make the user > identifiers a protected resource. Fetch the user identifier with an access > token and it returns basic profile information as well as if the access > token was issued by that specific user. > > > > Thanks for all of the feedback and support both virtually and in person! I'm > planning to move this proposal into GitHub next week (and work with Eran to > actually format it like a spec) so that changes are easier to keep track of. > > > > --David > > _______________________________________________ > specs mailing list > [email protected] > http://lists.openid.net/mailman/listinfo/openid-specs > > > -- > http://hi.im/santosh > > _______________________________________________ specs mailing list [email protected] http://lists.openid.net/mailman/listinfo/openid-specs
