SSO Requirements

[technicalen]

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

[sdurga · Accepted solution]

Hi,

SSO does not require client certificates for the operation. Which GP client version  and windows host are using ? Try restarting the GP service.

[technicalen]

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.

[sdurga]

you might want to open a case with support, this looks like an issue on the client side as it works with 1.1.4 and not with 1.1.6

[essnet]

Hello

Were you able to fix your problem? What was the cause and/or the fix ?

[bsanders]

Hello

Same question: Were you able to fix your problem? What was the cause and/or the fix ?

[rrau]

Any fix?  I am experiencing same problem with v1.2.1

[essnet]

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

[rrau]

"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.

[essnet]

It can fail on so many parts .... Enable debugging on the client and read logs. It will tell you if the clients tries to do SSO at all and many other information.

[bsanders]

Hello all, I just received information from Palo Alto Networks, that SSO doesn't work on (VMware) virtual machines. This seems not to be a bug, but "a limitation".

[SCoupland]

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.

[rrau]

the client machines are not virtual.