How to migrate from deprecated Google+ Sign-in API to the new Google Identity platform in a MVC project?

user_590790 0
Viewed 1078

A few days ago I was notified via email that Google is deprecating its Google+ APIs:

On March 7, 2019, all Google+ APIs and Google+ Sign-in will be shut down completely. This will be a progressive shutdown beginning in late January, with calls to these APIs starting to intermittently fail as early as January 28, 2019.

I currently use Google+ Sign-in as an external login provider in my ASP.NET MVC project. Seemingly, the ASP.NET documentation has not yet been updated (at the time of writing) to take into account this deprecated API.

Is there any guide available on whether or not the AddGoogle() extension method can still be used in the AuthenticationBuilder middleware, if so, how? If not, where can I find guidance on how to migrate from Google+ to the Google Identity Platform?

asp.net-core-mvc google-signin
2 Answers

There is an open issue on this on the aspnet\docs Github page.

This seems to be a breaking change, as indicated by the following issues on Github:

Apparently the Google OAuth provider performs a call to https://www.googleapis.com/plus/v1/people/me, which is used to get profile information. As stated by ThoughtHopper, "[t]he current code works until it tries to retrieve the userinfo."

A temporary workaround was posted by Tratcher, which is claimed to work for ASP.NET 2.0 and later:

.AddGoogle(o =>
        {
            o.ClientId = Configuration["google:clientid"];
            o.ClientSecret = Configuration["google:clientsecret"];
            o.UserInformationEndpoint = "https://openidconnect.googleapis.com/v1/userinfo";
            o.ClaimActions.Clear();
            o.ClaimActions.MapJsonKey(ClaimTypes.NameIdentifier, "sub");
            o.ClaimActions.MapJsonKey(ClaimTypes.Name, "name");
            o.ClaimActions.MapJsonKey(ClaimTypes.GivenName, "given_Name");
            o.ClaimActions.MapJsonKey(ClaimTypes.Surname, "family_Name");
            o.ClaimActions.MapJsonKey("urn:google:profile", "profile");
            o.ClaimActions.MapJsonKey(ClaimTypes.Email, "email");
            o.ClaimActions.MapJsonKey("urn:google:image", "picture");
        })

This changes the endpoint from which information is retrieved (no longer relying on Google+) and changes the way user info is mapped since this has changed.

From the amount of attention these issues are receiving I expect an update to be pushed out by Microsoft in the near future. Until then, this fix should work with the Google+ API disabled.

user_5907900

This answer is .NET Framework only.

It should already be solved by the Katana project nowdays, so as answered here:

Just update the package Microsoft.Owin.Security.Google to version 4.0.1.

You can read more here.

Or see a workaround for .NET Framework 4+ here.

user_43676830
Related