title: Google Authentication : OAuth2.0 Vs OpenID Connect
body: <p>I am evaluating the possible options provided by Google for adding google signin in my web application. The possible options as i see are</p>
  
  <ol>
  <li>Google+ Signin</li>
  <li>OAuth2.0</li>
  <li>OpenID Connect ( OAuth2.0 for Login )</li>
  </ol>
  
  <p>I didnt go with 1st one as it limits the API calls i can make in a day to 10000</p>
  
  <p>Out of 2 &amp; 3, i am inclined to go for 3rd. I dont really need API authorization and i am not concerned about access token expiration in my case. Once i receive user profile from Google, my web app will manage its own session of the user and does not need to query Google for any other data related to the user. And as per Google documentation, #3 allows me to customize User consent screen, while 1 &amp; 2 dont.</p>
  
  <p>Any comments on my comparison between 2 &amp; 3 ?</p>