Authenticating your client to Cloud Endpoints without a Google Account login

Question

I have been doing extensive research on how to authenticate your client (Android, iOS, web-app) with Cloud Endpoints without requiring your user to use their Google account login the way the documentation shows you.

The reason for this is that I want to secure my API or "lock it down" to only my specified clients. Sometimes I will have an app that does not have a user login. I would hate to pester my user to now sign in just so my API is secure. Or other times, I just want to manage my own users like on a website and not use Google+, Facebook, or whatever else login authentication.

To start, let me first show the way you can authenticate your Android app with your Cloud Endpoints API using the Google Accounts login as specified in the documentation. After that I will show you my findings and a potential area for a solution which I need help with.

(1) Specify the client IDs (clientIds) of apps authorized to make requests to your API backend and (2) add a User parameter to all exposed methods to be protected by authorization.

public class Constants {       public static final String WEB_CLIENT_ID = "1-web-apps.apps.googleusercontent.com";       public static final String ANDROID_CLIENT_ID = "2-android-apps.googleusercontent.com";       public static final String IOS_CLIENT_ID = "3-ios-apps.googleusercontent.com";       public static final String ANDROID_AUDIENCE = WEB_CLIENT_ID;        public static final String EMAIL_SCOPE = "https://www.googleapis.com/auth/userinfo.email";     }   import com.google.api.server.spi.auth.common.User; //import for the User object      @Api(name = "myApi", version = "v1",          namespace = @ApiNamespace(ownerDomain = "${endpointOwnerDomain}",          ownerName = "${endpointOwnerDomain}",          packagePath="${endpointPackagePath}"),          scopes = {Constants.EMAIL_SCOPE},           clientIds = {Constants.WEB_CLIENT_ID, Constants.ANDROID_CLIENT_ID,                       Constants.IOS_CLIENT_ID,                       Constants.API_EXPLORER_CLIENT_ID},                       audiences = {Constants.ANDROID_AUDIENCE})      public class MyEndpoint {          /** A simple endpoint method that takes a name and says Hi back */         @ApiMethod(name = "sayHi")         public MyBean sayHi(@Named("name") String name, User user) throws UnauthorizedException {             if (user == null) throw new UnauthorizedException("User is Not Valid");             MyBean response = new MyBean();             response.setData("Hi, " + name);              return response;         }      }  

(3) In Android call the API method in an Asynctask making sure to pass in the credential variable in the Builder:

class EndpointsAsyncTask extends AsyncTask<Pair<Context, String>, Void, String> {         private static MyApi myApiService = null;         private Context context;          @Override         protected String doInBackground(Pair<Context, String>... params) {             credential = GoogleAccountCredential.usingAudience(this,             "server:client_id:1-web-app.apps.googleusercontent.com");             credential.setSelectedAccountName(settings.getString(PREF_ACCOUNT_NAME, null));             if(myApiService == null) {  // Only do this once                 MyApi.Builder builder = new MyApi.Builder(AndroidHttp.newCompatibleTransport(),                         new AndroidJsonFactory(), credential)                     // options for running against local devappserver                     // - 10.0.2.2 is localhost's IP address in Android emulator                     // - turn off compression when running against local devappserver                     .setRootUrl("http://<your-app-engine-project-id-here>/_ah/api/")                     .setGoogleClientRequestInitializer(new GoogleClientRequestInitializer() {                         @Override                         public void initialize(AbstractGoogleClientRequest<?> abstractGoogleClientRequest) throws IOException {                             abstractGoogleClientRequest.setDisableGZipContent(true);                         }                     });                     // end options for devappserver                  myApiService = builder.build();             }              context = params[0].first;             String name = params[0].second;              try {                 return myApiService.sayHi(name).execute().getData();             } catch (IOException e) {                 return e.getMessage();             }         }          @Override         protected void onPostExecute(String result) {             Toast.makeText(context, result, Toast.LENGTH_LONG).show();         }     } 

What is happening is that in your Android app you are showing the Google account picker first, storing that Google account email in you shared preferences, and then later setting it as part of the GoogleAccountCredential object (more info on how to do that here).

The Google App Engine server receives your request and checks it. If the Android Client is one of the ones you specified in the @Api notation, then the server will inject the com.google.api.server.spi.auth.common.User object into your API method. It is now your responsibility to check if that User object is null or not inside your API method. If the User object is null, you should throw an exception in your method to prevent it from running. If you do not do this check, your API method will execute (a no-no if you are trying to restrict access to it).

You can get your ANDROID_CLIENT_ID by going to your Google Developers Console. There, you provide the package name of your Android App and the SHA1 which generates for you an android client id for you to use in your @Api annotation (or put it in a class Constants like specified above for usability).

I have done some extensive testing with all of the above and here is what I found:

If you specify a bogus or invalid Android clientId in your @Api annotation, the User object will be null in your API method. If you are doing a check for if (user == null) throw new UnauthorizedException("User is Not Valid"); then your API method will not run.

This is surprising because it appears there is some behind the scenes validation going on in Cloud Endpoints that check whether the Android ClientId is valid or not. If it is invalid, it won't return the User object - even if the end user logged in to their Google account and the GoogleAccountCredential was valid.

My question is, does anyone know how I can check for that type of ClientId validation on my own in my Cloud Endpoints methods? Could that information be passed around in an HttpHeader for example?

Another injected type in Cloud Endpoints is the javax.servlet.http.HttpServletRequest. You can get the request like this in your API method:

@ApiMethod(name = "sayHi")             public MyBean sayHi(@Named("name") String name, HttpServletRequest req) throws UnauthorizedException {                  String Auth = req.getHeader("Authorization");//always null based on my tests                 MyBean response = new MyBean();                 response.setData("Hi, " + name);                  return response;             }          }   

But I am not sure if the necessary information is there or how to get it.

Certainly somewhere there must be some data that tells us if the Client is an authorized and specified one in the @Api clientIds.

This way, you could lock-down your API to your Android app (and potentially other clients) without ever having to pester your end users to log in (or just create your own simple username + password login).

For all of this to work though, you would have to pass in null in the third argument of your Builder like this:

MyApi.Builder builder = new MyApi.Builder(AndroidHttp.newCompatibleTransport(), new AndroidJsonFactory(), null)

Then in your API method extract whether or not the call came from an authenticated client, and either throw an exception or run whatever code you wanted to.

I know this is possible because when using a GoogleAccountCredential in the Builder, somehow Cloud Endpoints knows whether or not the call came from an authenticated client and then either injects its User object into the API method or not based on that.

Could that information be in the header or body somehow? If so, how can I get it out to later check if it is there or not in my API method?

Note: I read the other posts on this topic. They offer ways to pass in your own authentication token - which is fine - but your .apk will still not be secure if someone decompiles it. I think if my hypothesis works, you will be able to lock-down your Cloud Endpoints API to a client without any logins.

Custom Authentication for Google Cloud Endpoints (instead of OAuth2)

Authenticate my "app" to Google Cloud Endpoints not a "user"

Google Cloud Endpoints without Google Accounts

EDIT: We used Gold Support for the Google Cloud Platform and have been talking back and forth with their support team for weeks. This is their final answer for us:

"Unfortunately, I haven't had any luck on this. I've asked around my team, and checked all of the documentation. It looks like using OAuth2 is your only option. The reason is because the endpoint servers handle the authentication before it reaches your app. This means you wouldn't be able to develop your own authentication flow, and would get results much like what you were seeing with the tokens.

I would be happy to submit a feature request for you. If you could provide a little more information about why the OAuth2 flow doesn't work for your customers, I can put the rest of the information together and submit it to the product manager."

(frowny face) - however, maybe it is still possible?

Answer 1

I have implemented Endpoint Auth using a custom header "Authorization" and it works just fine. In my case this token is set after login but should work all the same with your app. Check your tests because the value should be there. The way to retrieve that header is indeed:

String Auth = req.getHeader("Authorization");

You could take it a step further and define your own implementations of an Authenticator and apply it to your secure API calls.