Do I need to use OpenID or enough OAuth?

Question

I am working on a web project in which we use custom Google feeds and we store some information about them in our database. We don’t want users to create accounts with us, but instead they sign up using their Google credentials. It’s clear to me that we will need OAuth, but I’m interested in learning about the OpenID part. Is there uniquely identifiable user information that we can access through OAuth to track their data through sessions at our end? If so, what is the advantage of OpenID?

Answer 1

OpenID and OAuth (theoretically, if not in practice) are used for two separate functions:

OpenID is an identity management tool and minimizes account creation. Example. I want to use my Google account to log in wherever I go.

OAuth is a means of exchanging user information in a controlled, but open / compatible manner. Example. I want to allow Twitter to access my Google contacts without providing Twitter with a Google username and password.

This means that OpenID is required for login situations. If you need access to user data, you need OAuth. Some services, such as Twitter, have chosen a login through OAuth, but this is the wrong protocol use the most.

, OpenID + OAuth, , . Google . Google , .

, , .

Answer 2

, - . OpenID. , .