<?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: Authentication Policy Use Case in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/authentication-policy-use-case/m-p/345373#M86324</link>
    <description>&lt;P&gt;set up an authentication policy for 'known-user' which will trigger a new authentication window only if the user is already known through app-id&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="2020-08-25_15-28-48.png" style="width: 848px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/27498i0CA5A2C7E83F60A1/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="2020-08-25_15-28-48.png" alt="2020-08-25_15-28-48.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 25 Aug 2020 13:31:27 GMT</pubDate>
    <dc:creator>reaper</dc:creator>
    <dc:date>2020-08-25T13:31:27Z</dc:date>
    <item>
      <title>Authentication Policy Use Case</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/authentication-policy-use-case/m-p/345074#M86286</link>
      <description>&lt;P&gt;Here use case and wondering if this is feasible.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1. User Bob is already authenticated and connected(tunnel VPN) to firewall A with GlobalProtect with his account "Bob".&lt;/P&gt;&lt;P&gt;2. User Bob need to access critical ressource behind the same firewall A with, however, his privilege account "Bob-Priv".&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Problem, its look like the authentication policy is never triggered because user Bob is already authenticated with account "Bob".&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there a way to achieve this ?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 22 Aug 2020 15:14:41 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/authentication-policy-use-case/m-p/345074#M86286</guid>
      <dc:creator>DLONGPRÉ</dc:creator>
      <dc:date>2020-08-22T15:14:41Z</dc:date>
    </item>
    <item>
      <title>Re: Authentication Policy Use Case</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/authentication-policy-use-case/m-p/345373#M86324</link>
      <description>&lt;P&gt;set up an authentication policy for 'known-user' which will trigger a new authentication window only if the user is already known through app-id&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="2020-08-25_15-28-48.png" style="width: 848px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/27498i0CA5A2C7E83F60A1/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="2020-08-25_15-28-48.png" alt="2020-08-25_15-28-48.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 25 Aug 2020 13:31:27 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/authentication-policy-use-case/m-p/345373#M86324</guid>
      <dc:creator>reaper</dc:creator>
      <dc:date>2020-08-25T13:31:27Z</dc:date>
    </item>
    <item>
      <title>Re: Authentication Policy Use Case</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/authentication-policy-use-case/m-p/345403#M86328</link>
      <description>&lt;P&gt;It's not working.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The user is never triggered with the captive portal auth page. I think, this is because the firewall is already aware of Bob account that came from User ID Agent. However, I want that auth rule is triggered &amp;nbsp;to let user login with his priviledge account.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 25 Aug 2020 15:45:52 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/authentication-policy-use-case/m-p/345403#M86328</guid>
      <dc:creator>DLONGPRÉ</dc:creator>
      <dc:date>2020-08-25T15:45:52Z</dc:date>
    </item>
    <item>
      <title>Re: Authentication Policy Use Case</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/authentication-policy-use-case/m-p/345409#M86329</link>
      <description>&lt;P&gt;Is the rule matching the proper source zone/subnet, destination zone/subnet etc?&lt;/P&gt;&lt;P&gt;Have you tried setting set 'user' field to any?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If that also fails, try 'select' and set 'bob' as the user that needs to authenticate&lt;/P&gt;</description>
      <pubDate>Tue, 25 Aug 2020 16:13:30 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/authentication-policy-use-case/m-p/345409#M86329</guid>
      <dc:creator>reaper</dc:creator>
      <dc:date>2020-08-25T16:13:30Z</dc:date>
    </item>
    <item>
      <title>Re: Authentication Policy Use Case</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/authentication-policy-use-case/m-p/345850#M86400</link>
      <description>&lt;P&gt;Okay, Captive Portal was not triggered because the destination was HTTPS, and SSL decryption is required for Captive Portal to "redirect" HTTPS traffic.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also, notice that UserID database is always updated with latest user account logged. &amp;nbsp;That could cause problem in "big" environment where multiple accounts (normal, priviledge ..) are required to touch specific ressources. &amp;nbsp;I think that dedicated firewall(s) or VSYS isolated from the "normal USERID Database" could be a solution to front specific secure environment, like critical database, PCI... etc. &amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 28 Aug 2020 13:27:15 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/authentication-policy-use-case/m-p/345850#M86400</guid>
      <dc:creator>DLONGPRÉ</dc:creator>
      <dc:date>2020-08-28T13:27:15Z</dc:date>
    </item>
    <item>
      <title>Re: Authentication Policy Use Case</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/authentication-policy-use-case/m-p/345896#M86411</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;Just allow user Bob and then he must authenticate with Bob-Priv. Unless the resource is does not have an authentication method available?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;</description>
      <pubDate>Fri, 28 Aug 2020 20:49:32 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/authentication-policy-use-case/m-p/345896#M86411</guid>
      <dc:creator>OtakarKlier</dc:creator>
      <dc:date>2020-08-28T20:49:32Z</dc:date>
    </item>
  </channel>
</rss>

