Google OAuth vs LDAP for Hexnode Access on macOS and WindowsSolved

Participant
Discussion
3 days 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 (1)

Marked SolutionPending Review
Hexnode Expert
3 days 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 Settings for open/manual enrollment
  • Admin > Apple Business Manager / DEP > Automated Device Enrollment for macOS ADE enrollment
  • Enroll > Platform-Specific Enrollment > 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

Save