One option is to identify the 3 rd party credential provider that’s interfering with GlobalProtect SSO and evaluate the need for that.
There are 2 options to solve this problem. However, users may not easily identify the GlobalProtect tile. When the user logs in to this Windows computer using the tile that corresponds to 3 rd party credential provider GlobalProtect SSO would fail.įor GlobalProtect SSO to work on this Windows 7 computer, users have to select the GlobalProtect login tile first, then login to Windows. The screenshot below shows the login screen from a Windows 7 computer that has GlobalProtect and another credential provider. Or, the login screen may show only one login tile for the user, but selecting Switch User may show additional login tiles for that same user. However, if the computer has multiple credential providers, then the login screen typically shows multiple login tiles for the same user, one tile for each credential provider. If GlobalProtect is the only credential provider on a Windows 7 computer, users will not notice any change in their Windows login screen and GlobalProtect SSO works automatically. GlobalProtect SSO on Windows 7 and Windows Vista We include tips on how you can get GlobalProtect SSO to work as expected and provide the best login experience for users. For example, there can be other third-party credential providers on a Windows computer that might interfere and break GlobalProtect SSO. This document also describes scenarios that may affect GlobalProtect SSO on Windows. This document describes how the Windows user login experience has changed between Window 7 and Windows 8, 10 and the impact it has on GlobalProtect SSO. GlobalProtect uses Microsoft's credential provider framework to collect the user’s login credentials during the Windows login and transparently authenticate the user to the GlobalProtect portal and gateway. GlobalProtect SSO on Windows allows GlobalProtect agents to use Windows login credentials to authenticate with the GlobalProtect portal and gateway.
0 kommentar(er)
