Why do I have to log in twice on my Mac with Hexnode Access?Solved

Participant
Discussion
2 days ago May 08, 2026

Hi team, I’ve just deployed Hexnode Access to our fleet of MacBook Pros, but my users are complaining about a clunky experience. When they start the Mac, they have to log in to the Hexnode screen first, and then they are immediately met with the standard macOS login screen to log in again. Is there any way to bypass that second login and go straight to the desktop after the Hexnode screen? 

Replies (1)

Marked SolutionPending Review
Hexnode Expert
19 hours ago May 09, 2026
Marked SolutionPending Review

Thanks for raising this question. 

This behavior occurs because Hexnode Access and macOS serve two different security purposes. The Hexnode screen verifies your corporate cloud identity via your Identity Provider (IdP), while the native macOS login acts as the “gatekeeper” that unlocks the local user profile and the FileVault-encrypted disk.  

Without proper synchronization, the Mac doesn’t know that the person who just signed into the Hexnode window is the same person authorized to unlock the local hardware. 

To fix this, you need to ensure the cloud and local accounts are synchronized so they can perform a virtual “handshake.” Depending on your setup, you can follow these general steps to minimize the friction: 

  • Enable Password Sync: Navigate to your Hexnode Access Policy and ensure that Local Password Sync is enabled. This ensures the cloud password and local Mac password stay identical. 

  • Configure Account Provisioning: If you are using Google Workspace, leverage the integration settings to provision the local account directly from cloud credentials during the first sign-in. 

  • Migrate Accounts: For Microsoft Entra ID or Okta users, check the option to “Migrate local account to network accounts” to bridge the gap between existing local profiles and new cloud logins. 

  • Verify FileVault Settings: Ensure your policy is configured to pass the credentials through to FileVault, which is often the primary reason the secondary “native” screen appears. 

Please do reach out if you have any more queries. 

Regards, 
Mary Romero 

Save