<?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: Multiple DNS Names SSL Certificate in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/multiple-dns-names-ssl-certificate/m-p/29863#M21825</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Just as an update... have received the certificates from the CA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Managed to get them installed eventually after some tweaking to get the certificate chains to work. the certificates had the "alternative subject name" as the second FQDN of the other company vpn and all is working as expected.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;vpn.comany-a.com and vpn.company-b.com resolve to the same IP and have no cert errors.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the help&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Marc&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 08 Jul 2011 12:14:01 GMT</pubDate>
    <dc:creator>migration</dc:creator>
    <dc:date>2011-07-08T12:14:01Z</dc:date>
    <item>
      <title>Multiple DNS Names SSL Certificate</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/multiple-dns-names-ssl-certificate/m-p/29859#M21821</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this is an easy one to answer.&lt;/P&gt;&lt;P&gt;I have a customer that requires that the SSL-VPN have 2 fqdn names associated with it&lt;/P&gt;&lt;P&gt;i.e.&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="https://vpn.company-A.com"&gt;https://vpn.company-A.com&lt;/A&gt;&lt;SPAN&gt; = 196.1.1.1&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="https://vpn.company-B.com"&gt;https://vpn.company-B.com&lt;/A&gt;&lt;SPAN&gt; = 196.1.1.1&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How would i over come this as I can only allocate a single certificate to the VPN portal ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Marc&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 23 Jun 2011 13:45:34 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/multiple-dns-names-ssl-certificate/m-p/29859#M21821</guid>
      <dc:creator>migration</dc:creator>
      <dc:date>2011-06-23T13:45:34Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple DNS Names SSL Certificate</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/multiple-dns-names-ssl-certificate/m-p/29860#M21822</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Marc,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If they are two different companies, can they not have two portals and two IP's?&amp;nbsp; Then of course different certs?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;James&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 23 Jun 2011 14:41:25 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/multiple-dns-names-ssl-certificate/m-p/29860#M21822</guid>
      <dc:creator>James</dc:creator>
      <dc:date>2011-06-23T14:41:25Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple DNS Names SSL Certificate</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/multiple-dns-names-ssl-certificate/m-p/29861#M21823</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;They are the same company but with 2 domain names associated&lt;/P&gt;&lt;P&gt;With the current vpn solution they are using I think they have both certificates associated with the IP.&lt;/P&gt;&lt;P&gt;I will however confirm if this is the case of if they have 2 public addresses associated with their current VPN.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Marc&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 23 Jun 2011 16:07:02 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/multiple-dns-names-ssl-certificate/m-p/29861#M21823</guid>
      <dc:creator>migration</dc:creator>
      <dc:date>2011-06-23T16:07:02Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple DNS Names SSL Certificate</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/multiple-dns-names-ssl-certificate/m-p/29862#M21824</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Marc,&lt;/P&gt;&lt;P&gt;Just to clarify, are you asking if Palo Alto supports multidomain certificates, like these -&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.comodo.com/business-security/digital-certificates/multi-domain-ssl.php"&gt;http://www.comodo.com/business-security/digital-certificates/multi-domain-ssl.php&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://help.godaddy.com/article/3908"&gt;http://help.godaddy.com/article/3908&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;James&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 23 Jun 2011 16:27:39 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/multiple-dns-names-ssl-certificate/m-p/29862#M21824</guid>
      <dc:creator>jcostello</dc:creator>
      <dc:date>2011-06-23T16:27:39Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple DNS Names SSL Certificate</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/multiple-dns-names-ssl-certificate/m-p/29863#M21825</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Just as an update... have received the certificates from the CA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Managed to get them installed eventually after some tweaking to get the certificate chains to work. the certificates had the "alternative subject name" as the second FQDN of the other company vpn and all is working as expected.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;vpn.comany-a.com and vpn.company-b.com resolve to the same IP and have no cert errors.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the help&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Marc&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 Jul 2011 12:14:01 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/multiple-dns-names-ssl-certificate/m-p/29863#M21825</guid>
      <dc:creator>migration</dc:creator>
      <dc:date>2011-07-08T12:14:01Z</dc:date>
    </item>
  </channel>
</rss>

