How does OpenID authentication work?

99
votes

I am a little curious to know about how OpenID authentication works.

Is there any difference between OpenID authentication and the authentication which sites use exclusively for themselves?

1
authenticationopenid
Not a dup, but this one is very useful stackoverflow.com/questions/318677/… – Paul Tomblin
I think this is a dupe: stackoverflow.com/questions/123671/how-is-openid-implemented If no one disagrees then I'll close it in a few. – EBGreen
The link is more how to implemented open id. Here is how it works (how open id works with authentification and not how it works if someone would like to add it to his website). I think? – Patrick Desjardins
Ehh...that's fine. I was borderline anyway. I have a feeling a lot of the answers will cover the same info. – EBGreen
I think it's a duplicate from this one : stackoverflow.com/questions/69076/openid-login-workflow – Patrick Desjardins

1 Answers

100
votes

What is OpenID?

OpenID is an open, decentralized, free framework for user-centric digital identity. OpenID takes advantage of already existing internet technology (URI, HTTP, SSL, Diffie-Hellman) and realizes that people are already creating identities for themselves whether it be at their blog, photostream, profile page, etc. With OpenID you can easily transform one of these existing URIs into an account which can be used at sites which support OpenID logins.

OpenID

Difference between OpenID and conventional authentification form?

The difference is that the identification will be decentralized to an external site (for example Wordpress, Yahoo, ...). The website will know whether or not the identification is OK and let you login. Conventional website authentication performs a comparison with data held in a private database, so your username and password can be used to login to this website only. With OpenID you can use the same credentials on multiple websites.

How it works?

Steps

  1. User connects to OpenID enabled website.
  2. User enters credential information.
  3. A POST is made with a BASE64 (website to provider)
  4. An answer is built (that contains expiration)
  5. The website redirects the user to the provider to login.
  6. User enters password and submit.
  7. Verification is done.
  8. Login!