OpenID Connect does not look to be building on any of the OpenID technology.
Connect is Discovery + OAuth 2.0 + a standard identity API. Clearly this is useful for a set of web use cases. An alternative approach is to solve discovery with the appropriate components from the "Hammer stack" OR use the OpenID v.Next discovery; and define a standard identity API similar to what Portable Contacts did. Labelling this as OpenID seems to be hijacking the OpenID brand. On 2010-05-24, at 5:39 PM, Allen Tom wrote: > Hey guys, > > If the proposers believe that OAuth2 implementors need a standards based > identity API, then it is within the charter of the OIDF to take the lead on > this. > > Allen > > > On 5/24/10 3:44 PM, "Dick Hardt" <[email protected]> wrote: > > >> I think that if you want to build identity on top of OAuth, that you should >> write an OAuth extension. > _______________________________________________ specs mailing list [email protected] http://lists.openid.net/mailman/listinfo/openid-specs
