Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Google Workspace accounts which require setting up a lock screen password do not work #1726

Open
VesperLlama opened this issue May 24, 2022 · 4 comments · May be fixed by #2296
Open
Labels

Comments

@VesperLlama
Copy link

Describe the bug
My University provided Google account requires a lock screen password to be set to use it. It doesn't have any problem when I log in with MicroG but I cannot use the account on any app even after I set up a lock screen password. Apps like FairEmail or even GMail cannot access the account.

To Reproduce
Steps to reproduce the behavior:

  1. Add a account with Mobile Management turned on.
  2. Add a lock screen password.
  3. Try to log in to that account on other apps like FairEmail, GMail or Youtube.
  4. The apps show the added account but cannot access it.

Expected behavior
The apps should be able to access it when lock screen password is enabled.

System
Android Version: 12
Custom ROM: CrDroid 8.5

@aximut
Copy link

aximut commented May 2, 2023

Same here, any updates or workarounds?

@Umang96
Copy link

Umang96 commented Sep 26, 2023

Maybe something related to screen lock is missing in the AuthRequest? @ale5000-git @mar-v-in

09-26 18:23:08.846  1897  4075 W GmsAuthenticator: java.io.IOException: Error=DeviceManagementScreenlockRequired
09-26 18:23:08.846  1897  4075 W GmsAuthenticator: 	at org.microg.gms.common.HttpFormClient.request(HttpFormClient.java:95)
09-26 18:23:08.846  1897  4075 W GmsAuthenticator: 	at org.microg.gms.auth.AuthRequest.getResponse(AuthRequest.java:245)
09-26 18:23:08.846  1897  4075 W GmsAuthenticator: 	at org.microg.gms.auth.AuthManager.requestAuth(AuthManager.java:282)
09-26 18:23:08.846  1897  4075 W GmsAuthenticator: 	at org.microg.gms.auth.loginservice.AccountAuthenticator.getAuthToken(AccountAuthenticator.java:97)
09-26 18:23:08.846  1897  4075 W GmsAuthenticator: 	at android.accounts.AbstractAccountAuthenticator$Transport.getAuthToken(AbstractAccountAuthenticator.java:244)
09-26 18:23:08.846  1897  4075 W GmsAuthenticator: 	at android.accounts.IAccountAuthenticator$Stub.onTransact(IAccountAuthenticator.java:282)
09-26 18:23:08.846  1897  4075 W GmsAuthenticator: 	at android.os.Binder.execTransactInternal(Binder.java:1159)
09-26 18:23:08.846  1897  4075 W GmsAuthenticator: 	at android.os.Binder.execTransact(Binder.java:1123)

@ale5000-git
Copy link
Member

Related to #896

@d3mystified
Copy link

The workaround is to disable mobile management if you control the Workspace org.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants