<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Forward Trust Certificate in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/forward-trust-certificate/m-p/40277#M29557</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Suhaimi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Whenever there are certificate warnings with SSL websites, it means there's something about the certificate presented that the client browsers do not trust.&lt;/P&gt;&lt;P&gt;You should be able to use the existing certificate as long as you import the cert into your firewall along with its private key, and that certificate is included in the Trusted Root CA store on your staff's workstations (if it is a root CA certificate).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the existing certificate is not a root CA cert, make sure that you also import the root CA's cert that signed that certificate into the PAN. If this step is not done, the firewall will not pass the entire certificate chain to the internal hosts and since the infomation about the root CA is missing, there would always be a warning that the cert is not trusted.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here are some documents related to this problem and how to chain a certificate with its root cert to be imported into the PAN.&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" href="https://live.paloaltonetworks.com/docs/DOC-2287"&gt;https://live.paloaltonetworks.com/docs/DOC-2287&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" href="https://live.paloaltonetworks.com/docs/DOC-1327"&gt;https://live.paloaltonetworks.com/docs/DOC-1327&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" href="https://live.paloaltonetworks.com/docs/DOC-4289"&gt;https://live.paloaltonetworks.com/docs/DOC-4289&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;tasonibare&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 24 Dec 2013 10:58:37 GMT</pubDate>
    <dc:creator>tasonibare</dc:creator>
    <dc:date>2013-12-24T10:58:37Z</dc:date>
    <item>
      <title>Forward Trust Certificate</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/forward-trust-certificate/m-p/40276#M29556</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In my office environment, we have an internal certificate that we have been using prior to installing PAN device. Lately after installing PAN, our office staff are always getting certificate warnings whenever they visit a SSL enabled website. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I read in the PAN documents that a self-signed certificate generated by PAN firewall will eliminate this certificate warnings. My question is, do I need to generate a new self-signed certificate or can I use our internal certificate for connection to Internet?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 24 Dec 2013 04:49:17 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/forward-trust-certificate/m-p/40276#M29556</guid>
      <dc:creator>Suhaimi</dc:creator>
      <dc:date>2013-12-24T04:49:17Z</dc:date>
    </item>
    <item>
      <title>Re: Forward Trust Certificate</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/forward-trust-certificate/m-p/40277#M29557</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Suhaimi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Whenever there are certificate warnings with SSL websites, it means there's something about the certificate presented that the client browsers do not trust.&lt;/P&gt;&lt;P&gt;You should be able to use the existing certificate as long as you import the cert into your firewall along with its private key, and that certificate is included in the Trusted Root CA store on your staff's workstations (if it is a root CA certificate).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the existing certificate is not a root CA cert, make sure that you also import the root CA's cert that signed that certificate into the PAN. If this step is not done, the firewall will not pass the entire certificate chain to the internal hosts and since the infomation about the root CA is missing, there would always be a warning that the cert is not trusted.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here are some documents related to this problem and how to chain a certificate with its root cert to be imported into the PAN.&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" href="https://live.paloaltonetworks.com/docs/DOC-2287"&gt;https://live.paloaltonetworks.com/docs/DOC-2287&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" href="https://live.paloaltonetworks.com/docs/DOC-1327"&gt;https://live.paloaltonetworks.com/docs/DOC-1327&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" href="https://live.paloaltonetworks.com/docs/DOC-4289"&gt;https://live.paloaltonetworks.com/docs/DOC-4289&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;tasonibare&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 24 Dec 2013 10:58:37 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/forward-trust-certificate/m-p/40277#M29557</guid>
      <dc:creator>tasonibare</dc:creator>
      <dc:date>2013-12-24T10:58:37Z</dc:date>
    </item>
  </channel>
</rss>

