<?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 SSL Inbound Inspection  for single server hosting multiple websites in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/ssl-inbound-inspection-for-single-server-hosting-multiple/m-p/346324#M86505</link>
    <description>&lt;P&gt;We are looking to implement SSL Inbound Inspection for a single server.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;However a different certificate is used, based on the website being accessed.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My theory for the solution:&lt;/P&gt;&lt;P&gt;1. Create a custom URL Category for each individual website.&lt;/P&gt;&lt;P&gt;2.&amp;nbsp;Upload each website's certificate onto the Palo Alto&amp;nbsp;&lt;/P&gt;&lt;P&gt;3. Create an individual decryption policy for each website. In it identify Destination (Address/Zone), URL Category (custom URL category created in step 1), and the certificate for the particular website.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Has anyone encountered this requirement? Any feedback on if this solution would work?&lt;/P&gt;</description>
    <pubDate>Tue, 01 Sep 2020 22:49:11 GMT</pubDate>
    <dc:creator>JScottNaviH</dc:creator>
    <dc:date>2020-09-01T22:49:11Z</dc:date>
    <item>
      <title>SSL Inbound Inspection  for single server hosting multiple websites</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ssl-inbound-inspection-for-single-server-hosting-multiple/m-p/346324#M86505</link>
      <description>&lt;P&gt;We are looking to implement SSL Inbound Inspection for a single server.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;However a different certificate is used, based on the website being accessed.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My theory for the solution:&lt;/P&gt;&lt;P&gt;1. Create a custom URL Category for each individual website.&lt;/P&gt;&lt;P&gt;2.&amp;nbsp;Upload each website's certificate onto the Palo Alto&amp;nbsp;&lt;/P&gt;&lt;P&gt;3. Create an individual decryption policy for each website. In it identify Destination (Address/Zone), URL Category (custom URL category created in step 1), and the certificate for the particular website.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Has anyone encountered this requirement? Any feedback on if this solution would work?&lt;/P&gt;</description>
      <pubDate>Tue, 01 Sep 2020 22:49:11 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ssl-inbound-inspection-for-single-server-hosting-multiple/m-p/346324#M86505</guid>
      <dc:creator>JScottNaviH</dc:creator>
      <dc:date>2020-09-01T22:49:11Z</dc:date>
    </item>
    <item>
      <title>Re: SSL Inbound Inspection  for single server hosting multiple websites</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ssl-inbound-inspection-for-single-server-hosting-multiple/m-p/346480#M86521</link>
      <description>&lt;P&gt;That would work.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 02 Sep 2020 20:47:58 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ssl-inbound-inspection-for-single-server-hosting-multiple/m-p/346480#M86521</guid>
      <dc:creator>Abdul-Fattah</dc:creator>
      <dc:date>2020-09-02T20:47:58Z</dc:date>
    </item>
  </channel>
</rss>

