Hacker News new | past | comments | ask | show | jobs | submit login

The benefit is orders of magnitude better usability. I couldn't get users to grok OpenID, this just needs an email and password.

How will my mom log in to an SSL-certificate-requesting site from another computer?




This has pretty much the same end-user experience as OpenID, unless I'm misunderstanding something. The user still has to sign in to the IdP.


You're underestimating how familiar someone's email address is versus an OpenID URL whose significance the user doesn't know and whose use she can't grasp.


Agreed. URLs as an identifier are completely alien to non-technical folks. Even I think the notion is odd. They just don't make any sense. Plus they are hard to type correctly. Email addresses don't have these problems.


Although I think you're right, I can't understand why they didn't try to "fix" OpenID and started a new thing instead.

http://xkcd.com/927/

That said, I'd love they succeed and we have finally something that works well and it's not under company-X's control.


One of the reasons why we couldn't just "fix" OpenID is that we wanted a scheme that would be privacy-sensitive.

With OpenID, the result of the site redirecting you to the IdP (and then the IdP redirecting you back to the site) is that the IdP can get a trail of every website you're trying to log into. That's pretty fundamental to the way OpenID is designed.


In OpenID you have to enter your IDP URL and then optionally sign in to the IDP.

In Persona you will just click a button (because your browser knows your IDP) and then optionally sign in to your IDP. A huge difference.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: