Hey everyone, I recently discovered that we could use the Google Workspace credentials to sign in to a Windows device locally using Hexnode Access. I purchased the Secure LDAP service for my Google Workspace account, set up the LDAP client, and added the LDAP certificate for the configured client in Hexnode to enable authentication for the users in my organization when they sign in to their devices using their credentials. All was fine until the users tried to actually sign in to their devices. Now it keeps on displaying the Username and Password section only under “Login with a work account” without prompting the Google sign-in page (which I suppose must be displayed?). I can’t find any solution to this problem. Can somebody help me out?
I cannot enter sign in to my device using Google Workspace credentials when using Hexnode AccessSolved
Replies (6)
Hey @alice_grey , have you tried tinkering with the access permissions for the LDAP client you just created?
I noticed that the Verify user credentials setting was in the “no access” option by default, so I changed it to “Entire domain (Parent)”. That’s how it should work, right?
Yes, since you have changed it to the entire domain, all the users with a Google Workspace credential under your organization should be able to sign in to their devices using them. I am not sure what is happening here.
Hello @alice_grey , the changes made to the Google Admin Console settings for your LDAP Client will take up to 24 hours to take effect. Since the Verify user credentials access permission was set to Entire domain (Parent), the users in your organization will be able to sign in to their devices using their Google Workspace credentials after this time frame. When the user selects Login with a work account in the sign screen in their Windows device, the Google sign-in page asks for the email and further the password will be displayed, which the users can use to sign in to their Windows devices.
Regards,
Elle Reed,
Hexnode UEM.
The time frame is the issue here! @alice_grey , did your users try to sign in immediately after you set up the client?
Yes, they did try as soon as I set it up. Now we waited for 24 hours, and it worked perfectly. Thank you so much, @elle_reed and @emersyn .