I have a SharePoint server in a DMZ and would like to setup SSL Inbound Inspection. Is it possible to set this up if I am using third party (GoDaddy) certs? I tried exporting the cert from IIS and uploading to PA; it allows me to select in the inbound decryption policy but it is NOT decrypting the traffic.
Solved! Go to Solution.
Ok, it should work.... So... when you look in the logs, what are you seeing? Web-browsing on 443, just ssl being identified, etc.
Can you give me the process of how you exported and imported the cert file?
What format was the cert in? .DER format, .PEM format, etc. Did you do anything with the private key (that was provided by the IIS server).
Let us know, and we can try to help you out.
The logs are showing everything as just SSL; I checked the detailed information to make sure decrypted was not checked for those sessions. So nothing is being decrypted.
As far as the cert, I exported the cert from the IIS server into pfx format and entered a password to do so. I imported into the PA and entered the same password. The cert has the private key box checked.
I think the import may need to be in PEM format only (based on 4.1 Student Guide)
Key block needs to be encrypted with a passphase and chain of trust needs to be imported also.
I would try to see if this could be a solution.
Thanks for the reply.
1. I think the PAN may have imported it correctly as I was able to switch the web gui to using this cert (I have 4 SANs on the cert, one of them meant for the web gui of the PAN). I tested afterwards and my browser gets a green connection to it. This would imply that the PAN correctly has the public and private key, correct?
2. I have NOT imported the intermediate cert from GoDaddy. It comes in a p7b extension and the PAN cannot import this natively How would I convert it?
I think you may have imported a cert, however I still believe in following the student training documentation (which specifically states PEM format)
As for the command... use SSL Converter and it will do it for you.
If you want to be 100% certain, the best thing is to speak with the technical support group and get it from the experts.
Let the community know what you found to be the resolution.
Thanks for the info.
I went ahead and converted the intermed. cert and end cert to PEM and uploaded to the firewall. I am however now getting an error when I commit that it cannot complete the certificate chain for that certificate. I checked the PAN's Trusted Root CA section and GoDaddy IS listed. Ideas?
Hmmm, it seems that the FW does not have the complete certificate of trust chain from IIS up to the GoDaddy.
Can you confirm on your Device Certificate tab, that your imported IIS certificate has the usage type of Forward Untrust Certificate AND Forward Trust Certificate?
How did you import your certificate chain? I understand the IIS cert was converted and imported, I just am curious your steps that you took to import the certificate chain.
That is actually the document I followed to get the correct cert from IIS. GoDaddy provides two certs, the end cert and the intermed. cert. I uploaded the end cert from IIS and the Intermed cert. In the Cert. panel of the PAN UI, it correctly shows the end cert nested under the Intermed. cert.
I do NOT have the forward trust/untrust boxes checked because this is not for outgoing decryption. This is for inbound inspection.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the Live Community as a whole!
The Live Community thanks you for your participation!