topic Re: Trusted Root CA Not Installed on Client? in General Topics

Trusted Root CA Not Installed on Client?

CafNetMatt — Fri, 15 Jan 2016 01:45:12 GMT

This is on a PA-3020 running PAN-OS 7.0.4.

I've always manually chained certificates when installed an SSL certificate for Global Protect. I decided to see if I could install the SSL certificate and the Intermediate certificates separately and see if it would work. I configured Global Protect Portal > Agent Configuration > Trusted Root CA with the GoDaddy G2_G1 certificate provided by GoDaddy.

When I log into Global Protect, I do not get the 'untrusted certificate' error. However, when I check Keychain on my Mac, it only shows the client certificate installed, not the GoDaddy intermediate, and the certificate is labeled as 'signed by unknow authority'.

My questions:

1. Does the Global Protect client just check the Trusted Root CA but not push the certificate down to the client?

2. Is it still recommended to manually create the certificate chain or use this method?

The reason I'm trying not to chain them is because the client wants his SSL certificate to update via OCSP and it just doesn't do that if it's manually chained.

Thanks.

Re: Trusted Root CA Not Installed on Client?

pankaku — Fri, 15 Jan 2016 06:19:56 GMT

1. Does the Global Protect client just check the Trusted Root CA but not push the certificate down to the client?

It pushes the root ca to client. Client performs certificate checks when user connect to the GlobalProtect gateway.

2. Is it still recommended to manually create the certificate chain or use this method?

https://live.paloaltonetworks.com/t5/Management-Articles/How-to-Install-a-Chained-Certificate-Signed-by-a-Public-CA/ta-p/55523

Hope this helps!

Re: Trusted Root CA Not Installed on Client?

CafNetMatt — Fri, 15 Jan 2016 05:54:29 GMT

That's what's weird. I thought it pushed the Root CA to the client.

When I check Keychain on my Mac, the client's certificate is there but the CA Root is not. The client certificate just shows that's it's signed by an unknown signer.

I searched the keychain and could not find the Root CAs that should be being pushed down.

Regards,

Matt

Re: Trusted Root CA Not Installed on Client?

pankaku — Fri, 15 Jan 2016 06:06:30 GMT

It pushes the root ca to client. Client performs certificate checks when user connect to the GlobalProtect gateway.

Re: Trusted Root CA Not Installed on Client?

CafNetMatt — Fri, 15 Jan 2016 06:11:19 GMT

But I'm seeing it doesn't add it to the local keychain on the PC. Only the client certificate is being added.

Shouldn't the Root CA be added to the keychain?

Regards,

Matt

Re: Trusted Root CA Not Installed on Client?

pankaku — Fri, 15 Jan 2016 06:15:38 GMT

It will not be added.

From the admin guide:

"As a best practice, always deploy the trusted root CA certificates in the client configuration to ensure that the agents/apps perform the certificate checks to validate the identity of the gateway before establishing a connection. This prevents the agents/apps from falling prey to man-in-the-middle attacks"

Have you tried in windows system? May be godaddy intermediate root ca is not present on the local machine that's why it is showing was unknow signing authority.

Re: Trusted Root CA Not Installed on Client?

pankaku — Fri, 15 Jan 2016 06:19:14 GMT

Check this doc:

https://live.paloaltonetworks.com/t5/Management-Articles/How-to-Install-a-Chained-Certificate-Signed-by-a-Public-CA/ta-p/55523

Re: Trusted Root CA Not Installed on Client?

pankaku — Fri, 15 Jan 2016 07:15:39 GMT

I guess certificate chain will help here.

Re: Trusted Root CA Not Installed on Client?

CafNetMatt — Tue, 26 Jan 2016 00:57:25 GMT

Sorry for the delay.

So the choices become:

1. Manually chained. Then the Mac's keychain will show the certificate as complete.

2. Leave as is. The client gets no error during GP login but the keychain on the machine just shows the cert signed by an unknown CA.

User's don't actually go there to check anyway. They just don't want to see those pesky pop-ups about untrusted cert. So, I'm going to leave it as is.

Thank you for the response.