VPN Gateway fails to authenticate clients with new certificate uploaded

[m.shah.alizada2000]

Dear all,

We have a Palo Alto VPN gateway at our office, where our clients and customer’s Palo Alto connects to!

Our certificate at one of our customers site has expired and the vpn connection is down and hence to the isp!

Now I have generated a private key, using that I have generated a CSR sent the CSR to the CA and they have returned the public cert back to me!

I used OpenSSL to combine the main cert the two intermediate certs, the root cert and the private key into one pfx (pkcs12) file!

Then I uploaded the certs (pfx cert, root and intermediate certs) into the Palo Alto.

Now this is what I did. I uploaded the cert into the vpn gateway and client can’t connect ( I wanted to test and see if this works in the gateway then should be working in the client Palo Palo).

But this completely failed.

can any one help me figure this out please???

There are two attachment I have uploaded one of them is the client expired cert and the other one is the my machine failing to authenticate with the vpn gateway!

please help I need it by this Friday!

#paloalto

#certificate

#vpngateway

[JayGolf]

Hi @m.shah.alizada2000 ,

I see you mentioned you had combined the main cert the two intermediate certs, the root cert and the private key into one pfx (pkcs12) file. However, in your screenshot, I see the root cer, int certs, and wildcard is separate.

Are you saying your SEC360 wildcard cert is the result of this? You already look to have the cert chain imported individually and that looks correct as the root ca is at the top with the intermediate certs within the root ca. 

Try splitting the bundle so your wildcard is its own cert with the private key. Once that’s done, attach the wildcard cert to your SSL/TLS service profile that you use for the Portal/GW config.