Does anyone find the Hexnode Access for Widnows a bit strange?Solved

Hi, thanks for your input regarding Hexnode Access!

When Limit Offline Access option is enabled in Hexnode Access, users are required to re-authenticate with the configured identity provider (such as Google Workspace) at specified intervals, like every login, every 15 days, or every 30 days. This helps ensure that user access remains tightly controlled and up to date.

However, if the device doesn’t have internet access at the time re-authentication is required, the user won’t be able to log in, even if they know the local device password, because the system needs to verify credentials with the identity provider (IdP) online.

If you choose to disable Limit Offline Access, users will only need to authenticate with the IdP once, typically during their first login. After that, they can log in using the local password, even without an internet connection.

While disabling Limit Offline Access may seem to reduce the influence of the identity provider, it’s important to note that Hexnode Access still enforces strict access control at the point of initial login. Only users in your IdP can access the device in the first place. Even without frequent re-authentication, Hexnode Access ensures that only authorized users ever gain access.

Hexnode Access is built to support a wide range of organizational policies. If your organization demands tight security with continuous identity validation, enabling Limit Offline Access is recommended. For organizations that prioritize user flexibility, disabling this option allows continued access post-authentication even offline without compromising the integrity of access control.

Feel free to reach out if you have any further questions. We are here to help!

Regards,
Ben Clarke
Hexnode UEM