OpenID as a Single Sign On option? [closed]

Question

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.

Closed 7 years ago.

I'm just looking for different opinions. Do you consider OpenID a good "Single Sign On" solution?

The way it works seems to be a little bit confusing for an average user and there could be problems related to "putting all your eggs in the same basket".

Anyway, have anyone tried to implement his own OpenId solution within the context of an Intranet where there are many different applications (Wordpress, Elgg, Media Wiki, ..)??

I consider it could be a great solution to solve the "Digital Identity" problem but I don't know if it will work with the "login once and surf the Intranet" problem.

Opinions?

Answer 1

It's not such a usability problem on stack overflow since all the users are programmers anyway, but i can't think of many other sites that could get away with it.

I think openID will improve over time though and once all the sites using it start implementing all the features (like auto-filling the about me stuff) it'll be more worthwhile.

Answer 2

OpenID of course doesn't solve that problem. For example, if I use OpenID to sign in to StackOverflow, it doesn't mean I don't need to sign in to another website again using the same openID. -- tj9991

It can mean that, though. If your sign-on on the OpenID site is rememberd (for example, through cookies), you would effectively only need to sign on once per browser session (or once per week, once per month...) for all OpenID sites you visit.

Browser support and an API could even do away with the password prompt and the page redirect. Great idea!