Menu
Does anyone have experience with implementing OpenID on a non technical website? If you do, how were your non tech users reacting to the concept of OpenID and creation of the account on a different website?
I really like the idea of a single sign-on, but I am afraid that non-tech people who are used to create an account on every website would find it to complicated or even suspicious.
I know I could implement both (and that might be the route I will have to go) but I am trying to avoid implementing custom user login.
Also if you have links to some successful non-tech websites using OpenID only, it would be appreciated.
353
Is OpenID Dead? Yes, OpenID is an obsolete standard that is no longer supported by the OpenID Foundation.
Many developers believe that OpenID Connect is simpler to implement because there's no XML handling. OpenID lacks user authorization data (such as permissions) and focuses primarily on identity assertion. SAML is an identity data exchange and is very feature-rich. Authentication is decentralized with OpenID.
OpenID Connect lets developers authenticate their users across websites and apps without having to own and manage password files. For the app builder, it provides a secure verifiable, answer to the question: “What is the identity of the person currently using the browser or native app that is connected to me?”
A wide variety of clients may use OpenID Connect (OIDC) to identify users, from single-page applications (SPA) to native and mobile apps. It may also be used for Single Sign-On (SSO) across applications.
Yahoo released their OpenID usability research results a while back. This will give you an insight on how OpenID is perceived by non-techies.
197
JanRain has some casestudies on OpenID usage at http://www.janrain.com/openid/casestudies
2
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
