<?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: URL Filtering in Vwire SSL Trust Question in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/url-filtering-in-vwire-ssl-trust-question/m-p/26616#M19430</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;Maybe you can use the mangement interface for that.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope help&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;V.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 15 Nov 2013 10:42:13 GMT</pubDate>
    <dc:creator>VinceM</dc:creator>
    <dc:date>2013-11-15T10:42:13Z</dc:date>
    <item>
      <title>URL Filtering in Vwire SSL Trust Question</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/url-filtering-in-vwire-ssl-trust-question/m-p/26614#M19428</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I have a customer who is currently only running the PA in vwire. They need to have custom URL filtering continue and override pages.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My question is what needs to be done to have the end users browsers trust the certificate in vwire?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I know in layer 3 mode I can use a pushed out trusted root certificate going to a L3 interface. Based on my testing, in vwire mode I need to use transparent filtering but even if I do that and create a wildcard certificate it doesn't trust the certificate, I think because it is going directly to IP address not a dns address. Any insights or being pointed in the right direction would be appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Oct 2013 13:33:33 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/url-filtering-in-vwire-ssl-trust-question/m-p/26614#M19428</guid>
      <dc:creator>bparker</dc:creator>
      <dc:date>2013-10-03T13:33:33Z</dc:date>
    </item>
    <item>
      <title>Re: URL Filtering in Vwire SSL Trust Question</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/url-filtering-in-vwire-ssl-trust-question/m-p/26615#M19429</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The URL filtering override pages work like the Captive Portal pages. The answer to the orginal question was there needs to be a layer 3 interface of some type on the device for it to use for the certificates. This can be accomplished with a loop-back interface or a regular layer 3 interface. Otherwise in transparent mode you will receive certificate errors on the clients.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 14 Nov 2013 15:13:28 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/url-filtering-in-vwire-ssl-trust-question/m-p/26615#M19429</guid>
      <dc:creator>bparker</dc:creator>
      <dc:date>2013-11-14T15:13:28Z</dc:date>
    </item>
    <item>
      <title>Re: URL Filtering in Vwire SSL Trust Question</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/url-filtering-in-vwire-ssl-trust-question/m-p/26616#M19430</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;Maybe you can use the mangement interface for that.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope help&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;V.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 15 Nov 2013 10:42:13 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/url-filtering-in-vwire-ssl-trust-question/m-p/26616#M19430</guid>
      <dc:creator>VinceM</dc:creator>
      <dc:date>2013-11-15T10:42:13Z</dc:date>
    </item>
  </channel>
</rss>

