Please STOP requiring Google profile info, and switch to the other endpoint!

Question

I know this change already took place some months ago, but I wanted to write about this now. Here's the situation:

• When I click on
• I login on my Gmail account and get :And I don’t have a public Google profile requiring me to create one (asking age; address; sex; favorite color…)but in my case, if I click onAccept then I'm forced to upgrade to a Google profile because of the new Stack Exchange OpenId login behaviour (which mean fulfilling street address; birthday; phone number; favourite colour…).
• If click onAnnuler(cancel) I get :

I created a Gmail account in the early beginning, I only had to fill in the password, name, and email address. I also find unfair that others providers don't have to provide this information while it is required for Google.
I can understand this for things like Facebook... But, not every Google account is a Google profile...

Also, let's be clear:

• No, I will never upgrade, the same way I would never create a social media profile (I really dislike the bboard effect of the concept).

• Do not try to convince me it's Google, because the message states the contrary and it perfectly work if I login using those other ways :

Update:

Ok, you are not using OpenId but Google+ Sign in (which is not really OAuth 2.0). According to the documentation, there are two endpoints, and using https://www.googleapis.com/auth/plus.login instead of https://www.googleapis.com/auth/profile prompt users to upgrade to a Google+ profile even if you only require an email address.
Anyway Google clearly states it : "Your app can either prompt those users to create a Google+ profile or not...", which means that Google requires you to upgrade to a Google profile only if requested.
I reported it to Google, but I already guess they’ll say it’s not on their end too.

Answer 1

It is absolutely Google's fault for deprecating their OpenID 2.0 provider in favour of their OAuth 2.0/OpenID Connect provider backed by Google+. Considering how much more annoying OAuth 2.0 is to set up I feel this was a huge mistake, but they were the ones who made it.

Stack Exchange only requests the scopes profile and email, which should not prompt you to upgrade to Google+ like the plus.login scope would. It's unclear if that's specifically what you're saying is happening in your case, but if it is it sounds like Google is misrepresenting those scopes and that's something that would have to be brought up with them.

Note that your workaround of putting in the Google OpenID 2.0 endpoint manually will stop working as of April 2015, when that service is finally taken offline by Google.

Answer 2

We can't use Google's OpenID endpoint anymore (even until April) because we regularly launch new sites and Google only keeps the endpoint alive for existing domains.

I just tested this with a Google sign-in without a G+ profile and I can't reproduce what you're seeing. We already use the profile scope as you so emphatically suggest, and there is no requirement on our end for someone to have a Google+ profile associated with their Google account.