ODK Service 2.0.6 - Google Authentication Failed

Support
1

Hi everyone,

We have been using google account authentication while setting up ODK Service (rev2.0.6). It has been working smoothly until yesterday. Now, it always throws this log which is not very informative:

D/VerifyServerSettingsFragment: 2021-01-14 12:09:56.167 [2131492903] [onClickVerifyServerSettings] timestamp: 1610600996167
D/VerifyServerSettingsFragment: 2021-01-14 12:09:56.168 [2131492903] [authenticateGoogleAccount] invalidated authtoken
I/VerifyServerSettingsActivity: 2021-01-14 12:09:56.196 [onPause]
I/VerifyServerSettingsActivity: 2021-01-14 12:09:56.782 [onStop]
android.accounts.AuthenticatorException: Unknown
at android.accounts.AccountManager.convertErrorToException(AccountManager.java:2525)
at android.accounts.AccountManager.access$700(AccountManager.java:162)
at android.accounts.AccountManager$AmsTask$Response.onError(AccountManager.java:2368)
at android.accounts.IAccountManagerResponse$Stub.onTransact(IAccountManagerResponse.java:107)
at android.os.Binder.execTransactInternal(Binder.java:1021)
at android.os.Binder.execTransact(Binder.java:994)

D/VerifyServerSettingsFragment: 2021-01-14 12:09:57.362 [2131492903] [tickleInterface] started
I/VerifyServerSettingsActivity: 2021-01-14 12:09:57.363 [onRestart]
I/VerifyServerSettingsActivity: 2021-01-14 12:09:57.363 [onStart]
I/VerifyServerSettingsActivity: 2021-01-14 12:09:57.363 [onResume]
I/VerifyServerSettingsActivity: 2021-01-14 12:09:57.363 [onResume] getting VerifyServerSettingsFragment
I/VerifyServerSettingsFragment: 2021-01-14 12:09:57.363 [2131492903] [onResume]
I/VerifyServerSettingsActivity: 2021-01-14 12:10:04.835 [onPause]
I/VerifyServerSettingsActivity: 2021-01-14 12:10:04.949 [onStop]

I wonder if there is Google App clientId setup somewhere in ODK that now fails the authentication.

Note: It failed in all testing conditions which is related to Android version and network.

1 Like
3

@Thien_Mai I am confused as far as I can tell there is not release with a version 2.0.6. We have a “version” number and a “revision” number for historical reasons.

Do you mean the pre-release “Alpha rev 206” from August 2016? Google Accounts support was removed because of deprecation of interfaces by Google and upcoming requirements about registering each application. From an open source reusable application perspective we could not register a application for every organization that gets embedded in the code.

Google Accounts support was removed several years ago because of the idea of a reusable software frameworks that did not require registration with Google.

The authorization string that was previously being used was “oauth2:https://www.googleapis.com/auth/userinfo.email”;

1 Like
4

@W_Brunette Thanks for your answer, and sorry for misleading title. Yes, I am running rev206 with Google authentication.

I just want to dig a bit deeper in why it is failed before making decision on using username/password authentication instead. From my understanding, there must be clientId registered with Google, and clientId is managed by ODK. Now, the registered clientId does not work anymore and it failed the authentication. Is that correct?

5

I do not know the answer on the exact cause, I was simply providing areas of concern why ODK-X does not currently support the usage.

1 Like
6

Thanks a lot @W_Brunette