<?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: Conditional rules for GP MFA auth? in GlobalProtect Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/conditional-rules-for-gp-mfa-auth/m-p/584501#M5275</link>
    <description>&lt;P&gt;Hi &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/37508"&gt;@JimMcGrady&lt;/a&gt; ,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;That is a very interesting question!&amp;nbsp; The only option you have for different authentication policies on the portal or gateway is OS.&amp;nbsp; That doesn't help.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;However, you can have clients select different gateways based upon countries, and the gateways can be configured with different authentication methods.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For example, you could have SAML for your portal login.&amp;nbsp; The login info is cached by the portal and sent to the gateway.&amp;nbsp; One gateway can have the same SAML, and the client will not be prompted for login again.&amp;nbsp; Another gateway could have the same SAML (so same creds) with MFA enabled, and those clients will be prompted for MFA.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;MFA is always recommended for RA VPN.&amp;nbsp; Another option you may consider is have a long cookie lifetime for the trusted country and a short lifetime for the untrusted countries.&amp;nbsp; As long as the cookie is not expired, users will not be prompted for MFA.&amp;nbsp; However, they will not be prompted for username and password either.&amp;nbsp; This is not the portal/gateway authentication cookie, but rather the IdP MFA authentication cookie.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Tom&lt;/P&gt;</description>
    <pubDate>Mon, 22 Apr 2024 14:59:39 GMT</pubDate>
    <dc:creator>TomYoung</dc:creator>
    <dc:date>2024-04-22T14:59:39Z</dc:date>
    <item>
      <title>Conditional rules for GP MFA auth?</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/conditional-rules-for-gp-mfa-auth/m-p/584438#M5273</link>
      <description>&lt;P&gt;Is it possible to apply conditional rules on a GlobalProtect login so the means of login can vary? For example; If a Windows client is operating within a particular country or public IP range, just require simple SAML user login and maybe AD machine membership. However, if the client is outside of the country/ip-range, prompt the user for an MFA login.&lt;/P&gt;</description>
      <pubDate>Mon, 22 Apr 2024 02:26:03 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/conditional-rules-for-gp-mfa-auth/m-p/584438#M5273</guid>
      <dc:creator>JimMcGrady</dc:creator>
      <dc:date>2024-04-22T02:26:03Z</dc:date>
    </item>
    <item>
      <title>Re: Conditional rules for GP MFA auth?</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/conditional-rules-for-gp-mfa-auth/m-p/584501#M5275</link>
      <description>&lt;P&gt;Hi &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/37508"&gt;@JimMcGrady&lt;/a&gt; ,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;That is a very interesting question!&amp;nbsp; The only option you have for different authentication policies on the portal or gateway is OS.&amp;nbsp; That doesn't help.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;However, you can have clients select different gateways based upon countries, and the gateways can be configured with different authentication methods.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For example, you could have SAML for your portal login.&amp;nbsp; The login info is cached by the portal and sent to the gateway.&amp;nbsp; One gateway can have the same SAML, and the client will not be prompted for login again.&amp;nbsp; Another gateway could have the same SAML (so same creds) with MFA enabled, and those clients will be prompted for MFA.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;MFA is always recommended for RA VPN.&amp;nbsp; Another option you may consider is have a long cookie lifetime for the trusted country and a short lifetime for the untrusted countries.&amp;nbsp; As long as the cookie is not expired, users will not be prompted for MFA.&amp;nbsp; However, they will not be prompted for username and password either.&amp;nbsp; This is not the portal/gateway authentication cookie, but rather the IdP MFA authentication cookie.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Tom&lt;/P&gt;</description>
      <pubDate>Mon, 22 Apr 2024 14:59:39 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/conditional-rules-for-gp-mfa-auth/m-p/584501#M5275</guid>
      <dc:creator>TomYoung</dc:creator>
      <dc:date>2024-04-22T14:59:39Z</dc:date>
    </item>
  </channel>
</rss>

