<?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 Meta Apps bypassing Captive Portal Authentication in Next-Generation Firewall Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/meta-apps-bypassing-captive-portal-authentication/m-p/1223923#M5688</link>
    <description>&lt;P&gt;Hi Everyone,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am asking your expert advise on this issue:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We have an AP in bridge mode that is directly connected to Palo Alto. The firewall acts as the dhcp server and the AP just extends/bridges the network wirelessly. This setup is for Wireless Connection of Guest users with a separate zone as well. We created only one common guest user and password to simplify it.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We followed the KB article:&amp;nbsp;&lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA14u000000CqbiCAC" target="_blank" rel="noopener"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA14u000000CqbiCAC&lt;/A&gt;&amp;nbsp;to create a captive portal and it was successul.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;However, the issue that we encountered is that when the end-users connect to the WiFi, they were able to access Meta Apps like Messenger and Instagram, even without logging their credentials in the captive portal after being redirected to the portal.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Any ideas on how to solve this one? Thank you&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;#ngfw #pa3220&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Any ideas on how to solve this one? Thank you.&lt;/P&gt;</description>
    <pubDate>Sun, 16 Mar 2025 06:26:53 GMT</pubDate>
    <dc:creator>zedexxx</dc:creator>
    <dc:date>2025-03-16T06:26:53Z</dc:date>
    <item>
      <title>Meta Apps bypassing Captive Portal Authentication</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/meta-apps-bypassing-captive-portal-authentication/m-p/1223923#M5688</link>
      <description>&lt;P&gt;Hi Everyone,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am asking your expert advise on this issue:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We have an AP in bridge mode that is directly connected to Palo Alto. The firewall acts as the dhcp server and the AP just extends/bridges the network wirelessly. This setup is for Wireless Connection of Guest users with a separate zone as well. We created only one common guest user and password to simplify it.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We followed the KB article:&amp;nbsp;&lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA14u000000CqbiCAC" target="_blank" rel="noopener"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA14u000000CqbiCAC&lt;/A&gt;&amp;nbsp;to create a captive portal and it was successul.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;However, the issue that we encountered is that when the end-users connect to the WiFi, they were able to access Meta Apps like Messenger and Instagram, even without logging their credentials in the captive portal after being redirected to the portal.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Any ideas on how to solve this one? Thank you&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;#ngfw #pa3220&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Any ideas on how to solve this one? Thank you.&lt;/P&gt;</description>
      <pubDate>Sun, 16 Mar 2025 06:26:53 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/meta-apps-bypassing-captive-portal-authentication/m-p/1223923#M5688</guid>
      <dc:creator>zedexxx</dc:creator>
      <dc:date>2025-03-16T06:26:53Z</dc:date>
    </item>
  </channel>
</rss>

