Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

What exactly will happen to Google OpenId Connect to OpenID 2.0 mapping on Jan 1, 2017?

According to The Google OpenID 2.0 migration timetable, "mapping of OpenID 2.0 identifiers to OAuth 2.0 identifiers will continue to work until January 1, 2017."

It is not 100% clear from the documentation what form this transition will take. Will requesting scope: "openid" or openid.realm: "something" begin to return an error? Or will the old openid value simply not be present in the response? The Google OpenId Connect Documentation still uses the request values in its example OpenID Connect authentication URI.

Does anyone have a better understanding of how exactly this is going away? Our approach is to drop the openid scope and the openid.realm, but we're trying to get better certainty on the exact form of the change.

like image 450
Brett Avatar asked Dec 22 '16 15:12

Brett


People also ask

Is OpenID Connect dead?

Is OpenID Dead? Yes, OpenID is an obsolete standard that is no longer supported by the OpenID Foundation.

How does OpenID 2.0 work?

OpenID Connect (OIDC) is an open authentication protocol that works on top of the OAuth 2.0 framework. Targeted toward consumers, OIDC allows individuals to use single sign-on (SSO) to access relying party sites using OpenID Providers (OPs), such as an email provider or social network, to authenticate their identities.

Is OpenID 2.0 deprecated?

Note: We deprecated OpenID 2.0 as of Friday May 31, 2019.

What is the difference between OpenID Connect and oauth2?

OAuth 2.0 is designed only for authorization, for granting access to data and features from one application to another. OpenID Connect (OIDC) is a thin layer that sits on top of OAuth 2.0 that adds login and profile information about the person who is logged in.


1 Answers

The openid scope relates to OpenID Connect, not OpenID 2.0 (it's confusing, I agree…). OpenID Connect is fully supported and not going away, so the openid scope is still completely supported.

Passing the openid.realm param after the mapping is turned down won't return an error, it's just that the old openid value may not be present in the response. So you should design your service to be able to gracefully handle the case where no OpenID 2.0 value is present in the response.

like image 126
William Denniss Avatar answered Oct 04 '22 00:10

William Denniss