Why use OpenID Connect instead of plain OAuth2?

Question

I just started to use OAuth 2.0 as a way to authenticate my users. It works great - I just use the identity/profile API of each provider to get a validated email address of the user.

Now I read about OpenID Connect and am a little bit confused.

What is the difference between OpenID Connect and using the identity API over OAuth2? Is it just that I have a standard profile API, so that I don't have to worry whether I get an "email" or an "emails" JSON back?

Or is there more to it, which makes the OpenID Connect approach more secure than my first approach?

Alright, I didn't know about "OpenID Connect", I understood it as "OpenID" + "Connect". I'm sure you've already checked this: http://softwareforallseasons.blogspot.fr/2011/10/oauth-vs-openid-connect.html + I suggest you edit your question so that it reads OAuth 2.0 instead of just OAuth. — Aki, Jun 21 '13 at 15:04
@Aki: yes, I've seen the blog post, but couldn't make anything of it. — rdmueller, Jun 22 '13 at 20:55
@Ralf: As I see it, you can build apps with oauth and authorize sharing or not of specific resources linked to the user account. Using openid connect, it is made easier, the provider doesn't have to implement its own layer above oauth to handle it and clients have a standard way to access data. — Aki, Jun 26 '13 at 08:06
"I just use the identity/profile API of each provider **to get a validated email address** of the user." This means that you need to restrict the set of allowed providers. An arbitrary provider doesn't guarantee validation. Alternatively you could reject email addresses that don't match the domain of the provider. — CodesInChaos, Nov 10 '13 at 15:16
As an article on [oauth.net states: OAuth 2.0 is not an authentication protocol](http://oauth.net/articles/authentication/). It's actually authorization framework. They recommend using OpenID Connect (which is based on OAuth 2.0) if you want authentication. — Jonas, Aug 11 '16 at 08:47
I found this YouTube video presentation quite helpful: [*OAuth 2.0 and OpenID Connect (in plain English)*](https://youtu.be/996OiexHze0) by Nate Barbettini. — Basil Bourque, Dec 03 '18 at 00:47

score 85 · Answer 1 · edited May 12 '15 at 10:55

85

OpenID connect will give you an access token plus an id token. The id token is a JWT and contains information about the authenticated user. It is signed by the identity provider and can be read and verified without accessing the identity provider.

In addition, OpenID connect standardizes quite a couple things that oauth2 leaves up to choice. for instance scopes, endpoint discovery, and dynamic registration of clients.

This makes it easier to write code that lets the user choose between multiple identity providers.

edited May 12 '15 at 10:55

Ionuț G. Stan

135
6

answered Dec 17 '13 at 03:33

flup

951
7
7

Are you sure your statement "OpenID connect will give you an access token plus an id token." is correct? I thought an application can have an id_token and share it with a different application and then get an access token from that application. OIDC rides on top of the OAuth2 protocol but you don't necessarily get both. Although, it may happen most of the time. – Thomas Lann Dec 17 '18 at 18:08
"OpenID connect will give you an access token plus an id token." >> For most cases this is correct and the way it's usually handled. You make *one* request that consists of "token id_token" as responseTypes and "openid" as scope, which will return both an access token and an id token at the same time. The ID token is meant to be for the client, while the access token is meant to be opaque to the client and is meant to be passed on in requests to the resource server to protect, such as an API or other backend. – Mathias Conradt Apr 08 '19 at 09:30
"I thought an application can have an id_token and share it with a different application and then get an access token from that application." >> You don't exchange an ID token for an access token, if that's what you meant. And both is issues by the authorization server / IdP, not from another application or resource server (although authorization server and resource server can sometimes be the same). – Mathias Conradt Apr 08 '19 at 09:31

score 31 · Answer 2 · edited Aug 21 '18 at 23:24

OAuth provides only and should only provides authorization using an access token. OpenID connect is built on OAuth 2 in order to provide user authentication information. However, it will not provide you a more robust implementation than OAuth (since it uses OAuth and add some extra interactions with a OpenID provider).

OpenID Connect 1.0 is a simple identity layer on top of the OAuth 2.0 [RFC6749] protocol. It enables Clients to verify the identity of the End-User based on the authentication performed by an Authorization Server, as well as to obtain basic profile information about the End-User in an interoperable and REST-like manner. OpenID Connect Core 1.0 - draft 17

OpenID connect provides you a "standard" way to obtain user identity. If you use OAuth and the API, you should adapt your request for each resource, which may not always provide the same information or may change over the time. And conceptually, you use OAuth to be allowed to use an API, not to authenticate an user.

As background, the OAuth 2.0 Authorization Framework [RFC6749] and OAuth 2.0 Bearer Token Usage [RFC6750] specifications provide a general framework for third-party applications to obtain and use limited access to HTTP resources. They define mechanisms to obtain and use Access Tokens to access resources but do not define standard methods to provide identity information. Notably, without profiling OAuth 2.0, it is incapable of providing information about the authentication of an End-User. OpenID Connect Core 1.0 - draft 17

Note that OpenID connect provides an id_token with some information about the user. However, if you want the whole set of information, you still need the access_token to request the OpenID provider to get the userinfo (which confused me the first time I saw it). That shows that requesting user information from an API or from the OpenID provider use almost the same method. See 5.3.1. userinfo request in the draft.

This answer is absolutely correct. Just wanted to point one minor thing out: "However, if you want the whole set of information, you still need the access_token to request the OpenID provider to get the userinfo" >> this isn't necessarily the case depending on the authorization server/broken used: it's also possible to already include the full profile inside the ID token = JWT token, or even any other information using custom claims; an example being https://auth0.com/docs/tokens/id-token#add-custom-claims. Then you don't need to do the /userinfo request anymore. — Mathias Conradt, Apr 08 '19 at 09:34

score 18 · Answer 3 · answered Feb 26 '15 at 04:12

OAuth is an authorisation protocol, providing a way to give authorisation to access a protected resource. A by-product of the authorisation process is that the user is authenticated.

Technically, OAuth does not have to give you any information about the user. What it provides is a validation that the user has given authority to the application to access some data. This is governed by the scope of the authorisation grant.

OpenID Connect provides a way for the application to retrieve information about the authenticated user. Most importantly it provides a level of assurance that the information is valid (as far as the authorisation server is concerned anyway). This can then be used to facilitate identity federation.

In the past, federation was achieved with OAuth by granting a scope that allowed access to the user's identity information. OpenID Connect standardises that scope.

The external provider still needs to support opend Id right? You can't just implement open id on top of existing oauth 2 providers as a client of those external services. — CMCDragonkai, Mar 13 '17 at 06:22

score 8 · Answer 4 · edited Mar 11 '20 at 13:30

OpenID Connect is a profile of OAuth2... defining an architecture that enables a person to authorize an identity provider to release certain user claims to a client (website / mobile application).

OAuth2 offers the Resource Owner Password Credential Grant, which is rightly maligned by IAM experts as "The Devil".

A common pattern for OpenID Connect API is three steps:
1) Get a code
2) Get tokens like the access_token, refresh_token, and id_token
3) Get user info which contains claims like username, email, etc.
The schema for the id_token, which is a JWT, is defined in the OpenID Connect scope, as are many other details.

Another reason to use OpenID Connect is that there is a secure solution for centralized authentication for mobile software (at least IOS and Android). The current best practice defined by Google is to use new security features that block a mobile application from seeing cookies or credentials in a web view. Google published the AppAuth IOS and Android libraries because they really don't want you to leak Google credentials! As of the time of this writing, there are several OpenID Providers (aka IDP's...) that support the Google OpenID Connect AppAuth software, including: Google, OKTA, Ping, and my product Gluu.

Summary

Relying on plain OAuth 2.0 for authentication is dangerous if you (the client) are just trusting ANY valid access token you receive that's associated with that user as a reliable indicator that you're receiving the request from the actual user, without knowing whether that access token was generated by the user trying to log into your site or if it was generated by the user logging into some other (malicious) website/app.

With OpenID Connect, you can just look inside the JWT ID token provided by incoming requests and see if that token was generated by the user logging into your app or if they were logging into some other web app.

But if you're using the "authorization code flow", i.e. the user is being directed to send your back-end the authorization code and your back-end is trading that for the access token, and then your back-end is saving a record of those access tokens, then you can just check any incoming request to see if the provided access token is one that you have generated, thereby preventing malicious apps from impersonating your user with an access token that was created when the user logged into the malicious app. If you do that check, you don't need to use OpenID Connect to avoid that kind of attack. But it seems that for some use-cases this method of saving and checking access tokens is either not possible or not convenient, and it's for those use-cases that OpenID Connect is necessary.

Key quotes from the article

"So [when using only OAuth 2.0] we wind up in the situation where any site the user logs into with their Facebook account can impersonate that user at any other site that accepts Facebook logins through the client-side flow (the default for Facebook). The less common server-side flow is more secure, but more complicated."
"The client has no way to tell who the authorization server thought it was issuing that access token to."

thanx. this is quite valuable. I wonder if I can/should change this to the valid answer... what will happen? — rdmueller, Mar 20 '22 at 21:19
@rdmueller My understanding is that the recommended practice on Stack Overflow is to set the best answer to be the 'accepted answer'. But I think SO will still generally show the top-rated answer at the top(?). — Nathan Wailes, Mar 20 '22 at 21:31

score 1 · Answer 7 · answered Oct 11 '13 at 13:52

1

Open id connect is build on the top of OAuth and hence it's more robust. OAuth is the protocol which is used only for the authorization and open id connect is very similar to OAuth but it combines the feature of OAuth also. You can start communication between your RP's and IP's using this protocol and their are various loop holes in OAuth protocol that's why better to use Open Id Connect.

answered Oct 11 '13 at 13:52

Utsav

149
2
7

Would be interesting to know why this answer got a downvote... – rdmueller Oct 11 '13 at 18:18
2

which loopholes are you referring to (honest curiosity).. I'm struggling with the same question as the OP. It seems oAuth2 (on which Openid Connect is based) already does authentication, although I'm familiar with the session-hijacking and MiM replay attackes possible with simple Bearer tokens. Are these the loopholes you're referring to? – Geert-Jan Oct 29 '13 at 20:48
7 years later... those loopholes surely aren't solved by OIDC though? You still have access tokens after all, and they still do the same thing they were supposed to do in OAuth2 in OIDC? It seems to me like if you have flaws in your implementation of OAuth2, layering OIDC on top isn't going to solve those problems. – Seer May 28 '20 at 08:47

Why use OpenID Connect instead of plain OAuth2?

7 Answers7

Summary

Key quotes from the article

Linked