--- title: "SSO(PLAP) client limitations" slug: "ssoplap-client-limitations" updated: 2026-01-22T16:19:13Z published: 2026-01-22T16:19:13Z canonical: "support.appgate.com/ssoplap-client-limitations" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.appgate.com/llms.txt > Use this file to discover all available pages before exploring further. # SSO(PLAP) client limitations Security based Policy in SSO to hide the last logged in username / user profiles from the login screen is not compatible with AppGate. Other limitations are also listed in the article. In the security policy of the SSO agent there is a setting that can be enabled that hides the last logged in username on the Client. This applies to windows clients (see [http://www.thewindowsclub.com/make-windows-7-8-use-classic-logon-screen](http://www.thewindowsclub.com/make-windows-7-8-use-classic-logon-screen) for more information on this setting in the security policy). If this policy is enabled, it causes an issue with the AppGate client that stops it from loading up and the user will not be able to login and connect. For information on the Windows SSO (PLAP) client, please refer to the Admin manual [here](/v1/docs/windows-sso-plap-client-v6-6#how-does-it-work). Other Limitations of the SSO (PLAP) Client - Once AppGate SDP SSO client is installed Local users can't use the normal AppGate SDP client. - Onboarding has to be done from the AppGate SDP SSO client for a user on a specific computer. If the user has already on-boarded using the normal AppGate SDP client, then the SSO client will fail. - Two factor authentication onboarding is not supported on AppGate SDP SSO client. - You should not set the Windows security policy to hide the last logged in username / user profiles from the login screen. A Policy is a set of rules that govern access control and permissions for users and devices within the Appgate ZTNA system. Policies determine what resources users can access based on their entitlements. The application used by end-users to connect to the Appgate ZTNA system, providing secure access to resources. Users added to the local database that are not listed in an external identity provider.