<?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: LDAP User based policy not working in Next-Generation Firewall Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/ldap-user-based-policy-not-working/m-p/580332#M2828</link>
    <description>&lt;P&gt;Yeah, fixed the issue.&lt;BR /&gt;Policy was not matching because of the username mismatch in the policy vs captive portal input username.&lt;/P&gt;</description>
    <pubDate>Thu, 14 Mar 2024 04:29:50 GMT</pubDate>
    <dc:creator>ArunKumar7</dc:creator>
    <dc:date>2024-03-14T04:29:50Z</dc:date>
    <item>
      <title>LDAP User based policy not working</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/ldap-user-based-policy-not-working/m-p/580169#M2816</link>
      <description>&lt;P&gt;Essentially, I aim to enable users to access the internet after being prompted with a captive portal and entering their LDAP username and password. Each user should have a separate policy. I have configured the LDAP server, portal, and other settings, but after entering credentials on the captive portal login page, the internet page does not load.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;My policy is set to allow any to any with the source user as the AD username. However, if I set the source user as "Any," then I am able to access the internet. Why is the internet not working when the source is set as an LDAP user? Can anyone provide assistance with this issue?&lt;/P&gt;</description>
      <pubDate>Wed, 13 Mar 2024 08:10:51 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/ldap-user-based-policy-not-working/m-p/580169#M2816</guid>
      <dc:creator>ArunKumar7</dc:creator>
      <dc:date>2024-03-13T08:10:51Z</dc:date>
    </item>
    <item>
      <title>Re: LDAP User based policy not working</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/ldap-user-based-policy-not-working/m-p/580192#M2819</link>
      <description>&lt;P&gt;what is the format you use in your security rule to identify the user (upn, san,...) and how are they actually mapped (show user ip-user-mapping all)&lt;/P&gt;
&lt;P&gt;the captured username needs to match the username in the security rule&lt;/P&gt;</description>
      <pubDate>Wed, 13 Mar 2024 10:49:47 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/ldap-user-based-policy-not-working/m-p/580192#M2819</guid>
      <dc:creator>reaper</dc:creator>
      <dc:date>2024-03-13T10:49:47Z</dc:date>
    </item>
    <item>
      <title>Re: LDAP User based policy not working</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/ldap-user-based-policy-not-working/m-p/580332#M2828</link>
      <description>&lt;P&gt;Yeah, fixed the issue.&lt;BR /&gt;Policy was not matching because of the username mismatch in the policy vs captive portal input username.&lt;/P&gt;</description>
      <pubDate>Thu, 14 Mar 2024 04:29:50 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/ldap-user-based-policy-not-working/m-p/580332#M2828</guid>
      <dc:creator>ArunKumar7</dc:creator>
      <dc:date>2024-03-14T04:29:50Z</dc:date>
    </item>
  </channel>
</rss>

