Setting up OAUTH for google, and they have advised that they cannot allow the request because the sign in image is not compliant with their branding requirements:
The Google sign-in button on your project’s homepage URL is not compliant with the Google sign-in branding guidelines. Please update the Google sign-in button on your website according to Google sign-in branding guidelines.
Thank you for your patience. Please reply back to this email after your project is in compliance with the requirements above.
To encourage users to click the button, we recommend the call-to-action text “Sign in with Google” or “Sign up with Google”. It should be clear to the user that they are signing in to your app or signing up for your app with their Google credentials, not signing up or registering for a Google account on your app.
However, we do need to use the colored Google icon (on a white background), not the white Font Awesome icon:
Regardless of the text, you can’t change the size or color of the Google “G” logo. It must be the standard color version and appear on a white background. If you need to create your own custom size Google logo, start with any of the logo sizes included in the download bundle.
I suspect you got an overzealous enforcement agent in this case, or else the policy must have changed very recently. Because this is the first we’ve ever heard of it in years of things working just fine.
Multicolor is impossible with fonts (mostly — there are technical ways it can work in some rare cases, but this is highly dependent on the operating system) so this will take quite some time to work out.
I think this checks most of the boxes for being acceptable by their standards. It doesn’t fit their padding specifications, but I wonder if the padding might be somewhat flexible under the “Matching your own app’s style” wiggle room they talk about. If you think this looks good, I can post the theme component for it.
@tshenry would be happy to try with the theme component you made to see if google accept it!
I’ve gotten the same e-mail today on my self-hosted forum.
I use Facebook, GitHub, Twitter, and Google logins. Today I received the “Action needed” e-mail telling me to be sure the sign-in button is compliant with the branding guidelines, and to reply to the e-mail when it is.
Is there something I can do locally, or is it best to wait for an update?
Edit: Sorry, missed @tshenry’s link. If anybody else missed it because they scroll too fast here it is:
I’ve added it to my default theme and hopefully it’s fine.
But I have another Discourse install that’s been running for a few years with Google login and it’s never been an issue. Perhaps this is only for new installs? They would have reviewed my older forum years ago, but my latest one is brand new from a couple of weeks ago.
Trying to set this up, Google is requiring a “review”. The review then complains that the sign-in button is “not compliant with the Google sign-in branding guidelines. Please update the Google sign-in button on your website according to Google sign-in branding guidelines.”
In typical Google manner, they don’t explain what exactly the issue is - I think it’s the “wrong” Google logo.
A quick fix would be to install the Compliant Google Login Button theme component. Based on the frequency of reports about this, it looks like we’ll have to come up with a permanent fix that doesn’t rely on a theme component.
Did they give you any more specific information? It seems like the problem might be that we say “with Google” instead of “Sign in with Google”? We can update these for all Discourse sites, but in the meantime you can also add the text right away in your admin settings:
go to admin > customize > text
search for js.login.google_oauth2.title
update the text to “Sign in with Google”
Since that text is longer, you’d also want to add some custom CSS to adjust spacing… (under admin > customize > themes)