Open
Conversation
Intune now sets a policy such that users are not allowed to create work profiles anymore. This is good in principle because users are never supposed to do this manually (and are, in fact, incapable of doing so). Our code is also affected because `WorkAccountService` triggered sign-in flow in `WorkAccountAuthenticator` through `AccountManager.addAccount`, which is the action prohibited by the policy. We can still (and need to) call `AccountManager.addAccountExplicitly` to register the account with the system.
like 3a68bc3 i.e. same fix as microg#3257
ale5000-git
reviewed
Mar 20, 2026
...rc/main/kotlin/com/google/android/gms/auth/account/authenticator/WorkAccountAuthenticator.kt
Outdated
Show resolved
Hide resolved
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Intune now sets a policy such that users are not allowed to create work profiles anymore. This is good in principle because users are never supposed to do this manually (and are, in fact, incapable of doing so). Our code is also affected because
WorkAccountServicetriggered sign-in flow inWorkAccountAuthenticatorthroughAccountManager.addAccount, which is the action prohibited by the policy → leading to popup "This setting is blocked. If you have any questions, contact your IT admin.". We can still (and need to) callAccountManager.addAccountExplicitlyto register the account with the system.I will provide some more cleanup this weekend. (edit, done)