Google OAuth vs LDAP for Hexnode Access on macOS and WindowsSolved

Participant
Discussion
3 weeks ago Oct 30, 2026

I’m setting up Google Workspace with Hexnode for macOS and Windows enrollment. I added Google Workspace as an OAuth integration because I want users to authenticate with Google credentials, filter out unwanted enrollments, and use Hexnode Access so we don’t have to manage separate local account provisioning.

After adding OAuth, the “Google User” option still appears unavailable/greyed out in some authentication settings. My Google Workspace plan does not include Secure LDAP. Can Google OAuth be used for Hexnode Access, or is LDAP required?

Replies (5)

Marked SolutionPending Review
Hexnode Expert
3 weeks ago Oct 30, 2026
Marked SolutionPending Review

Google OAuth and Google Secure LDAP are used for different parts of this workflow.

For enrollment authentication, Google OAuth can be used to authenticate users with their Google credentials during supported enrollment flows. Depending on the enrollment method, the relevant settings can be found under areas such as:

  • Admin > Enrollment for open/manual enrollment
  • Admin > Apple Business/School Manager > Automated Device Enrollment for macOS ADE enrollment
  • Enroll > Platform-Specific Enrollment > Windows > Windows PCs and Tablets for Windows enrollment

However, Hexnode Access with password synchronization and reduced local account management requires an LDAP-based directory connection. Google OAuth alone does not synchronize the Google account password with the local device account password.

If your Google Workspace plan does not include Secure LDAP, you can still use OAuth-based Google authentication where supported, but users must continue to maintain their local account passwords for initial setup, password changes, and offline fallback scenarios.

Regards,
Isabel Lora
Hexnode UEM

Marked SolutionPending Review
Participant
3 weeks ago Oct 30, 2026
Marked SolutionPending Review

So with OAuth only, users can sign in with Google during enrollment, but they still need to know their Mac or Windows local password later? I was hoping OAuth would remove that part completely.

Marked SolutionPending Review
Hexnode Expert
3 weeks ago Oct 30, 2026
Marked SolutionPending Review

Yes @thomas_m, OAuth can verify the user’s Google identity, but it does not provide the LDAP password sync needed to replace or manage the local device account password.

From the user’s perspective, the local account password is still required in cases such as:

  • First-time local account setup or verification
  • Password rotation or password mismatch scenarios
  • Offline login or fallback access

You can configure the online re-authentication interval for supported Hexnode Access workflows, but that does not remove the local password requirement when only OAuth is configured.

Regards,
Isabel Lora
Hexnode UEM

Marked SolutionPending Review
Participant
3 weeks ago Oct 30, 2026
Marked SolutionPending Review

That explains the greyed-out behavior I was seeing. I only had Google OAuth configured and no Secure LDAP available in the Google Workspace plan, so I was expecting an option that OAuth cannot actually enable for password sync.

Marked SolutionPending Review
Hexnode Expert
3 weeks ago Oct 30, 2026
Marked SolutionPending Review

Yes @r_foster , that is the expected limitation. To use Hexnode Access for LDAP-backed password synchronization or to minimize separate local password management, configure Google Workspace with Secure LDAP and then use that directory integration with the Hexnode Access policy.

If Secure LDAP is not available, the practical workaround is to continue with Google OAuth for enrollment authentication and keep local account password management in place.

Regards,
Isabel Lora
Hexnode UEM

Save