![]() Also this policy will not work if Self Service Mode is not set do Disabled. Now, at the Botton of the same link above there is something that didn't exist before the "Silent Authentication"Īs I understand: The SSO will be ignored even if enabled, if this policy is not configured to Enabled. And since the user does not have access to the workspace interface is not able to "force" the sign in. However, this also breaks Desktop Lock, since without the automatic logon, the desktop is not "subscribed" and ofc will not launch. Subsequent sessions logon seamlessly like should in the first time. When the user does this will not be asked for the password and the authentication happens and the shortcuts pop. ![]() Unless the user right click and click Refresh or click Sign In.(if Sign In is visible sometimes it's not.) I've been configuring Receiver/Workspace SSO for over a decade now and all that requirements checklist worked until latest versions of workspace app.įor those that don't know the steps to make SSO work look hereįor new user profiles, the Workspace App sits there and does not automatically logon for the user, no shortcuts are placed anywhere. ![]() Writing this so other people don't bash heads to the desks like I did! ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |