Question

On JellyBean device.

I’m following this to request an oauth2 token, e.g.

AccountManager am = AccountManager.get(getActivity());
am.invalidateAuthToken(MY_AUTH_TOKEN_TYPE, null);
am.getAuthToken(aGoogleAccount, MY_AUTH_TOKEN_TYPE, null, this, 
    new OnTokenAcquired(), new Handler(new OnError()));

and then make the check as per the later code sample:

private class OnTokenAcquired implements AccountManagerCallback<Bundle> {
@Override
    public void run(AccountManagerFuture<Bundle> result) {
        Bundle bundle = result.getResult();
        ...
        Intent launch = (Intent) bundle.get(AccountManager.KEY_INTENT);
        if (launch != null) {
            startActivityForResult(launch, 0);
            return;
        }
    }
}

I never get a KEY_INTENT. I understand the following:

There may be many reasons for the authenticator to return an Intent. It may be the first time the user has logged in to this account. Perhaps the user’s account has expired and they need to log in again, or perhaps their stored credentials are incorrect. Maybe the account requires two-factor authentication or it needs to activate the camera to do a retina scan. It doesn’t really matter what the reason is. If you want a valid token, you’re going to have to fire off the Intent to get it.

However, the getAuthToken always results in the permission screen, or login screen, appearing before the code hits the run method at which point the token is valid. I’ve tried:

1. Turning on 2 step authentication. Account login is requested before run so always have the token in run.
2. Changing the password on the server. Again account login is requested before run so always have the token in run.

Don’t have the ability to try a retina scan so somewhat at a loss.

EDIT 1 The problem I have is that there may be a circumstance where I will get a KEY_INTENT and so I’d rather test this code path now rather when when it’s out in the field.

Thanks in advance.

Peter.

Answer 1

Had a chance to do something similar on a project. This not the exactly the same as your code, and I still say that the callback docs have too many ‘maybes’ to be certain of how it should work, but if you use this method passing false for notifyAuthFailure, you will get an intent with the re-login screen if you change the password or enable 2FA. This is for ClientLogin, but should work similarly for OAuth 2 (not tested though). Something like:

// using Calendar ClientLogin for simplicity
Bundle authResult = am.getAuthToken(account, "cl", false, null, null).getResult();
if (authResult.containsKey(AccountManager.KEY_INTENT)) {
  Intent authIntent = authResult.getParcelable(AccountManager.KEY_INTENT);
  // start activity or show notification
}