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.
I am running GP 1.1.4 and when I connect to the customers portal SSO works (it sends my credentials even though I don't authenticate as I am not part of their AD) although this is probably the single sign on config from my GP config.
The customer is running GP 1.1.6 which I think was upgraded from 1.1.5 when the issue also occered.
"GlobalProtect Client SSO will work only if you use GP Credential Provider for Windows (automated with Windows XP, more tricky with Seven if you have third party providers like we do here) and of course if you open your Windows session with said user from same AD"
However, it is working on another FW we have that is on v1.6.1.. same exact enviroment.
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!