On 2010-7-21 20:15, Christopher Warner wrote:
It's just nomenclature. Essentially Aol, Yahoo, Google etc all provide
login via OpenID. However they also provide or use other Federated or
One sign-on to rule them all authentication systems. For instance;
Facebook has an openid endpoint (which tends to work sporadically); They
also have Facebook connect. Google tends to stick with email address or
OpenID. Aol the same.
Most of these services don't publicly advertise their use of OpenID as
it kills mindshare and brand. Why sign-in to facebook with openid when
you could sign in via Facebook connect which essentially gets one to
login and use Facebook services. Same with all the others. You won't see
Yahoo promoting Google by saying Did you know that you can login using
your Google account. Or vice versa. Since Plone as a CMS doesn't have
to be concerned about such things; we can be concerned about the overall
confusion the user must experience with the OpenID URL dialog and do so.
So, the idea is to concentrate solely on OpenID as the solution to
single sign on and as Plone already supports OpenID. It's a two bird one
stone equation. A user will understand logging into Yahoo or Google more
readily than providing an OpenID URL. Thus, technically, any way you
look at it. By easing the opportunity via a click, they are using
OpenID, which makes it* *an easy and ubiquitous solution.
What will the result be? Will people be able to use the email address
from their Google account on a Plone site? Or their facebook login?
Wichert.
--
Wichert Akkerman wich...@wiggy.net It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org/mailman/listinfo/framework-team
