topic Moving from Global Protect 1.1.6 -> 1.1.7 in General Topics

Moving from Global Protect 1.1.6 -> 1.1.7

rrau — Tue, 15 Jan 2013 15:22:02 GMT

I believe moving away from 1.1.6 now requires a trusted certificate? I have about 600 remote users on 1.1.6.. trying to get to the latest rev (1.2.1) without any user interruption. I tested with our QA firerwall and I am getting certificate errors.. is there any detailed instructions on how to proceed?

Re: Moving from Global Protect 1.1.6 -> 1.1.7

jpa — Tue, 15 Jan 2013 17:56:03 GMT

GP Client version 1.1.7 checks if the CN of the cert is valid. What that means is, if you are using a FQDN as the CN in the cert, the FQDN must the interface of the firewall the client connects to. If there is mismatch you will get cert errors. If you are not using FQDN, but using IP address, then the IP address must be the gateway IP address. If either one of this condition is not met, you will have to regenerate certs before you upgrade the GP client. To summarize

1) You will have to generate certs with right CN

2) on the portal download and activate GP client version 1.1.7 and set the upgrade to transparent

3) have the end user rediscover network.

That should take care of the upgrade.

Re: Moving from Global Protect 1.1.6 -> 1.1.7

darren_g — Tue, 22 Jan 2013 00:44:06 GMT

Sorry, can you just clarify this for me please?

You said

> if you are using a FQDN as the CN in the cert, the FQDN must the interface of the firewall the client connects to

The FQDN must WHAT the interface of the firewall the client connects to?

I connect my clients via a registered FQDN in my domain name (vpn.domain.com) in the GP client. My current certificate has the name as "vpn.domain.com", but the CN as the IP address of the interface.

Do I need to generate a new certificate with vpn.domain.com for name **and** CN??

thanks