Google OAuth login blocked in Android kiosk mode with Access DeniedSolved

Participant
Discussion
1 month ago Jul 14, 2026

I have an Android tablet enrolled as a fully managed device and locked in Hexnode kiosk mode. The kiosk app opens fine and shows the login screen, but when I tap the Google login button, it shows an “Access denied” screen and then the app closes/fades away.

I tried changing web kiosk settings and also tried allowing Chrome, but that did not fix it. Facebook login opens a web page as expected, but Google OAuth does not complete inside kiosk mode. What should be allowed for Google sign-in to work?

Replies (1)

Marked SolutionPending Review
Hexnode Expert
1 month ago Jul 14, 2026
Marked SolutionPending Review

Hi @harold,

This usually happens when the kiosk app triggers a separate Android or Google authentication component that is not allowed to run in the kiosk policy.

For Google OAuth, the app may call the Android Credential Manager / Google credential selector activity to display the Google account selection or authentication overlay. In strict kiosk mode, Hexnode can block this component as an unauthorized app, which results in the “Access denied” message.

To resolve it:

  1. Reproduce the issue on the device.
  2. Run a Scan Device action from Hexnode.
  3. Open the device in Manage > Applications > Blocked Packages.
  4. Check whether a Google credential selector or Android Credential Manager package/activity is listed, commonly shown with a name ending in CredentialSelectorActivity.
  5. Add that package/activity to Hexnode under Apps using its Bundle ID.
  6. Go to the Android kiosk policy.
  7. Navigate to Android Kiosk Lockdown > Background Apps.
  8. Add the newly created Android Credential Manager / Google credential selector entry as a background app.
  9. Save and deploy the policy to the device.

This allows the Google sign-in overlay to launch while keeping the device locked in kiosk mode.

Regards,
Sienna Carter
Hexnode UEM

Save