<?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: Generate Certificate  to be Signed by Public CA  for Global Protect VPN in Next-Generation Firewall Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/generate-certificate-to-be-signed-by-public-ca-for-global/m-p/550201#M1552</link>
    <description>&lt;P&gt;In addition to what&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/55733"&gt;@rmfalconer&lt;/a&gt;&amp;nbsp;said, be sure to add SAN entries ("Host Name" field under Certificate Attributes) for the certificate. CN (Common Name) is no longer used for hostname certificate validation, the SAN is. Also, you can have multiple SANs under a single certificate and you can have a single certificate that covers multiple Portals and Gateways.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I run a combined certificate with a default FQDN as the CN and all my explicit Portal and Gateway FQDNs as SANs on the same certificate. I.e. a CSR to be signed by an external auth with:&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;Certificate Name = VPN_Certs&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;Common Name = vpn.example.com&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;Signed By - External Authority&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;Certificate attributes:&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&amp;nbsp; County = US&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&amp;nbsp; State = Allstate&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&amp;nbsp; Locality = Anytown&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&amp;nbsp; Organization = Acme Corporation&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&amp;nbsp; Host name = vpn.example.com&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&amp;nbsp; Host name = vpn-portal-a.example.com&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&amp;nbsp; Host name = vpn-gateway-a.example.com&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&amp;nbsp; Host name = vpn-portal-b.example.com&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&amp;nbsp; Host name = vpn-gateway-b.example.com&lt;/P&gt;</description>
    <pubDate>Thu, 20 Jul 2023 17:28:44 GMT</pubDate>
    <dc:creator>Adrian_Jensen</dc:creator>
    <dc:date>2023-07-20T17:28:44Z</dc:date>
    <item>
      <title>Generate Certificate  to be Signed by Public CA  for Global Protect VPN</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/generate-certificate-to-be-signed-by-public-ca-for-global/m-p/549335#M1512</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We would like to use our GlobalProtect VPN using certificate signed by Public CA.&lt;/P&gt;
&lt;P&gt;As the CA team is requesting to generate CSR from Palo Alto Firewall , can I follow below article to generate?&lt;/P&gt;
&lt;P&gt;&lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClSxCAK" target="_blank"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClSxCAK&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;And we have two ISPs connected to PaloAlto Firewalls and we have two GlobalProtect VPN Gateways configured. If I want to use Public signed CA for both gateways , I need to generate separate CSR for each gateway right?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;And when generating CSR , in the common name session , can I use public ip address instead of FQDN?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Please help me to confirm.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 14 Jul 2023 03:07:54 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/generate-certificate-to-be-signed-by-public-ca-for-global/m-p/549335#M1512</guid>
      <dc:creator>EvanRaci</dc:creator>
      <dc:date>2023-07-14T03:07:54Z</dc:date>
    </item>
    <item>
      <title>Re: Generate Certificate  to be Signed by Public CA  for Global Protect VPN</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/generate-certificate-to-be-signed-by-public-ca-for-global/m-p/550193#M1551</link>
      <description>&lt;P&gt;You can follow that link to generate a CSR.&lt;/P&gt;
&lt;P&gt;You should generate a CSR on each node.&lt;/P&gt;
&lt;P&gt;Public authorities will not include IP addresses as CN or SAN entries. You'll need to use FQDN.&lt;/P&gt;</description>
      <pubDate>Thu, 20 Jul 2023 16:01:15 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/generate-certificate-to-be-signed-by-public-ca-for-global/m-p/550193#M1551</guid>
      <dc:creator>rmfalconer</dc:creator>
      <dc:date>2023-07-20T16:01:15Z</dc:date>
    </item>
    <item>
      <title>Re: Generate Certificate  to be Signed by Public CA  for Global Protect VPN</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/generate-certificate-to-be-signed-by-public-ca-for-global/m-p/550201#M1552</link>
      <description>&lt;P&gt;In addition to what&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/55733"&gt;@rmfalconer&lt;/a&gt;&amp;nbsp;said, be sure to add SAN entries ("Host Name" field under Certificate Attributes) for the certificate. CN (Common Name) is no longer used for hostname certificate validation, the SAN is. Also, you can have multiple SANs under a single certificate and you can have a single certificate that covers multiple Portals and Gateways.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I run a combined certificate with a default FQDN as the CN and all my explicit Portal and Gateway FQDNs as SANs on the same certificate. I.e. a CSR to be signed by an external auth with:&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;Certificate Name = VPN_Certs&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;Common Name = vpn.example.com&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;Signed By - External Authority&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;Certificate attributes:&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&amp;nbsp; County = US&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&amp;nbsp; State = Allstate&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&amp;nbsp; Locality = Anytown&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&amp;nbsp; Organization = Acme Corporation&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&amp;nbsp; Host name = vpn.example.com&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&amp;nbsp; Host name = vpn-portal-a.example.com&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&amp;nbsp; Host name = vpn-gateway-a.example.com&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&amp;nbsp; Host name = vpn-portal-b.example.com&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&amp;nbsp; Host name = vpn-gateway-b.example.com&lt;/P&gt;</description>
      <pubDate>Thu, 20 Jul 2023 17:28:44 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/generate-certificate-to-be-signed-by-public-ca-for-global/m-p/550201#M1552</guid>
      <dc:creator>Adrian_Jensen</dc:creator>
      <dc:date>2023-07-20T17:28:44Z</dc:date>
    </item>
  </channel>
</rss>

