Problem with certificate after upgrading GlobalProtect 1.1.7

[jmrodriguez]

Hi everybody.

Up to now, I've had working a Globalprotect configuration, with only a Server Certificate, and it worked very well.

After upgrading to version 1.1.7, I've received the message: "The paloalto.xxxxx.es certificate is not signed by a trusted certificate authority.". That is a problem for "no on demand" VPN connections, because you have to click "Continue" to make VPN connection work.

Do you know how I could solve this?

One solution is to create another certficate based on a Trusted CA certificate and send it to all the clients to install it, but it is difficult to do in our situation right now.

Could you help me please?

Thank you very much.

[bnelson]

Jim,

GlobalProtect 1.1.7 implements enhanced checks for CA Server Certificates chain-of-trust. This change will cause some existing configurations to become invalid and may result in remote users receiving an error when connecting to the portal, or will not be able to connect if the certificate issue is present on the gateway. Before deploying the GlobalProtect Agent 1.1.7 to users, ensure that the Portal and all Gateway server certificates are valid and that the certificate Common Name (CN) fields match the FQDN or IP address of the portal and/or gateway that uses the certificate.

The SSL certificate that you use for the GlobalProtect portal/gateway should have a Common Name (CN) that matches what you configured in the portal settings. For example, if your certificate has the CN of gp.example.com, ensure that your portal configuration lists the gateway as gp.example.com and does not use an IP address and vice versa, otherwise when the GlobalProtect Agent tries to connect it will generate an error specifying that the certificate CN does not match.

Additionally, when the certificate is created, the Subject Alternative Name (SAN) must be exactly the same as the certificate's CN. If the certificate uses the CN of the DNS name, ensure that the SAN also uses the DNS name and not the IP address. A mismatch will cause the GlobalProtect Agent to recognize that the SAN is not the same as the CN and will also produce the certificate error.

If your certificates are generated by a public certificate authority, then this will be done correctly and you should not have any issues.

Refer to the following tech note for details on configuring server certificates: https://live.paloaltonetworks.com/docs/DOC-2020

The workaround is to revert back to Global Protect 1.1.6 which does not check trusted CA.

Ben

[cmateam]

I'm getting this too. Any resolve?  I have a purchase certificate from a CA.  Portal has the correct CN in it also. I am getting a error on the user level that says "The certificate may have been compromised." "The certificate CN name mismatch. The certificate is not issued to XXX.XXX.XXX.XXX"

[gwesson]

cma_sateam:

Is your portal certificate issued to a domain name, like 'portal.example.com'? If yes, then in the GP client configuration you must specify that same name. It seems like it may be complaining that you are putting the public IP address in the GP client portal area, but the certificate is issued to a domain name instead of that IP.

Check both the firewall's portal settings and the GP client portal settings. Ensure that all the names match the certificate being used on the firewall's portal configuration.

-Greg Wesson

[cmateam]

The portal is specified by the domain name like portal.example.com on the firewall.  I will check the users client.