Android Enterprise enrollment shows Invalid Authentication for local users in HexnodeSolved

Participant
Discussion
4 weeks ago Sep 30, 2026

I’m trying to enroll an Android tablet into Hexnode using Android Enterprise QR code enrollment. On the Hexnode authentication page, the domain option only shows Local.

The local users are already visible under Manage > Users, and I tried using their permanent passwords. I also reset the user password from the portal, but every local user still gets an “Invalid Authentication” error during enrollment.

I changed the Android Enterprise enrollment profile from global authentication to enforced local user authentication, but the same error appears. Is there a way to get the tablet enrolled without being blocked at this authentication step?

Replies (1)

Marked SolutionPending Review
Hexnode Expert
4 weeks ago Sep 30, 2026
Marked SolutionPending Review

Hello @yuudai ,

For Android Enterprise enrollment, the authentication behavior depends on the User Authentication setting configured in the enrollment profile.

Since the local users are already present in Manage > Users and resetting the permanent password did not resolve the “Invalid Authentication” error, you can use the following workaround to complete enrollment first:

  1. Go to Enroll > Android Enterprise > Enrollment profiles.
  2. Open the enrollment profile used for the QR code enrollment.
  3. Go to User Authentication.
  4. Select No Authentication.
  5. Save the enrollment profile.
  6. Retry the Android tablet enrollment using the QR code.

This bypasses user credential validation during enrollment and allows the device to enroll successfully.

After the device is enrolled, assign the user manually: Manage > Endpoints > [select the device] > Actions > Edit > Change Owner.

No Authentication should be treated as a workaround, especially in controlled staging environments. It allows enrollment without validating user credentials, so if user-based authentication is required for your deployment workflow, local user authentication should be reviewed before enabling it again.

Regards,
Simon Scott
Hexnode UEM

Save