As with most things GlobalProtect I am having issues with a customer and am finding it difficult to find out why.
I guess the first question is do you need to use client certificates in order to use SSO with global protect?
The issue the customer has is although he has checked single sign on in the portal config he still has to enter his username an password in the global protect agent for it to work. If he doesn't enter the username and password we can see in the global protect service logs it is not sending a username etc, they all show as blank in the logs.
Looking between our config which works and their config which doesn't the only difference I can see is we hace client certs configured and they don't.
Any help is appriciated
Solved! Go to Solution.
With regards to SSO failing on VMware, this is due to the way authentication is handled by the virtualised OS which presents the credentials in a different way to a native OS which results in the SSO to apply an empty user and domain. The work around for this issue is to manually define the credentials and enable the check box for "Remember Me".
If you require SSO support on VMware then log a feature request with your SE to have SSO support on VMware added.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!