title: Restriction of Google OAuth call to Google Play unique name
body: <p><strong>Background</strong></p>
  
  <p>Reading these articles <a href="http://developer.android.com/google/auth/http-auth.html" rel="nofollow noreferrer">http://developer.android.com/google/auth/http-auth.html</a> and <a href="http://android-developers.blogspot.cz/2013/01/verifying-back-end-calls-from-android.html" rel="nofollow noreferrer">http://android-developers.blogspot.cz/2013/01/verifying-back-end-calls-from-android.html</a> and some other responses on so like <a href="https://stackoverflow.com/questions/14563155/oauth-2-0-client-id-and-client-secret-exposed-is-it-a-security-issue">Oauth 2.0: client id and client secret exposed, is it a security issue?</a> and <a href="https://stackoverflow.com/questions/19615372/client-secret-in-oauth-2-0">client secret in OAuth 2.0</a> I realized that it is not worth authorizing my rest api using a token received from Google Oauth. Anybody can fake it (doing his own app and getting the token) as the attackers can get the Client ID from a decompiled apk. I see as the only way of securing the app to use the app's unique name on Google Play.</p>
  
  <p><strong>Question</strong></p>
  
  <p>Is it possible to resstrict the call to Google to obtain the security token to the app's unique name on Google Play?</p>