Get flash to fully experience Pearltrees
They say the road to hell is paved with good intentions. Well, that’s OAuth 2.0 . Last month I reached the painful conclusion that I can no longer be associated with the OAuth 2.0 standard.
The Account Manager project aims to produce: A protocol definition that sites can use to define their account-and-session management features in a format a web browser can understand. (The latest draft of the specification is here ).
CardSpace ou la gestion des identités et accès Par Keith Brown et Mis à jour par Pierre Couzy Êtes-vous las de la gestion et de la sécurisation d'un ensemble toujours plus important de noms d'utilisateur et de mots de passe ? Êtes-vous las de remplir sans cesse des profils utilisateur pour des sites Web qui souhaitent glaner des informations personnelles vous concernant ? Aimeriez-vous faciliter la tâche des utilisateurs qui souhaitent se connecter à vos sites et services Web ? Êtes-vous préoccupé par le vol d'identité et le phishing ?
I’ve been thinking about how we make OpenID both easier and sexier for quite a while now. As frustrating as the answer may be to technologists, the problem is not necessarily one that can be solved with more technology. Instead, at some point, you have to move beyond the original constituents of a solution and start to package up the thing in a way that is less alienating, and less “insider baseball”. “OpenID Connect”, therefore, is what I’m starting to use in casual conversation as my answer to Twitter and Facebook Connect.
On Friday, David Recordon , one of the original authors of OpenID, released a single-page specification for OpenID Connect , a concept that I outlined on this blog in January before I joined Google . I’m particularly excited about this early proposal because it builds on all the great progress that the community has made recently on a litany of technologies, including OAuth 2.0 and the link-based resource descriptor format (LRDD) and its emerging JSON-based variant ( JRD ). But I’m most excited about OpenID Connect because it forces the OpenID community to evaluate the progress we’ve made over the last three years ( OpenID 2.0 was introduced in 2007 ) and to think critically about where we go next , and how we get there, given what the market has indicated it wants.