Hello,
I just came across a weird problem with the Horizon Client and Single Sign-On.
When I'm using the Horizon Client to connect to a desktop (linked clone), lock the Windows session, disconnect and then reconnect to the desktop, I'm presented with the Windows lock screen instead of being logged in automatically. The lock screen doesn't show the Ctrl+Alt+Del prompt though, so it looks like the SSO component already "pressed" Ctrl+Alt+Del but couldn't proceed with signing in.
When I restart the Horizon Client I can successfully connect to the desktop again (with SSO).
This doesn't happen with Zero Clients (Dell Wyse P25) or HTML Access.
Steps to reproduce:
- Open Horizon Client and connect to the View Connection Server
- Enter credentials
- Connect to a desktop by selecting one of the assigned pools
- Inside the session go to Start > Click the arrow next to Shut down > Lock
- Disconnect from the desktop by closing the session window (the main Horizon Client window is still open though!)
- From the main screen of the Horizon Client, re-connect to the desktop that was just locked
(Note: It actually doesn't matter to which desktop pool you'll connect, at this point SSO won't even work on desktops you haven't manually locked. So essentially, once you lock the screen in any Horizon Client session, SSO will stop working on any subsequent connections until the Horizon client is being restarted.) - You're presented with the Windows lock screen instead of being logged-in automatically
This is on Horizon View 6.1 with Client version 3.3.0.
Both "Discard SSO credentials" settings in the View Administrator are set to "Never".
Again, this problem doesn't occur when connecting through Zero Clients or HTML Access, so to me it looks like a bug within the Horizon Client.
Anything I might have missed?
Thanks in advance!
Best regards
Dan