title: Google Sign-In or OpenID Connect
body: <p>I've been trying to add authentication with Google OpenID Connect on my web app. I started with the OpenID Connect page of the documentation <a href="https://developers.google.com/identity/protocols/OpenIDConnect" rel="nofollow noreferrer">https://developers.google.com/identity/protocols/OpenIDConnect</a>. The steps are clear and I've been able to generate an URL that can authenticate users. Everything seems to work fine. User clicks on link, is directed to Google where she authenticates; she's then redirected to my app's endpoint where it exchanges the <code>auth_code</code> for an <code>access_token</code>, with the <code>state</code> returned matching what she has in <code>session['openid_state']</code>, etc. </p>
  
  <p>My problem now is to produce a proper branded button. The Google's OIDC documentation gives hint as to how you can create an authentication url, it does not show you how to make a button. I presume that you have to play with css, html, and some static files. I'd rather avoid this if possible.</p>
  
  <p>In the OIDC document, right from the start it tells you that if you want a "Sign-in with Google" you should use Google Sign-In. What does that mean? Should I use Google Sign-In instead of OIDC and abandon all steps currently described in the OIDC document? Or should I use it as an alternate way to quickly take care of the browser side?</p>
  
  <p>When I look at the Google Sign-In API I don't understand how my OIDC url fits, or where I can instead put params such as the <code>state</code>. Google Sign-In is said to be built on top of OIDC, how?</p>