<?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 Several client authentication in a Gateway in GlobalProtect Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/several-client-authentication-in-a-gateway/m-p/540032#M3975</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;we have a PA-850 running 10.1.8 firmware.&lt;/P&gt;
&lt;P&gt;We currently use GlobalProtect VPN using Symantec VIP authentication via RADIUS.&lt;/P&gt;
&lt;P&gt;We want to progressively migrate the authentication to Azure AD MFA (already synced with all accounts). I was wondering if I could simply add the new client authentication to the list and use it as a fall back authentication method.&lt;/P&gt;
&lt;P&gt;My approach was to remove user accounts one by one from Symantec Database. Then, the user opens global protect which first tries to authenticate against Symantec and after the failure falls back to Azure AD.&lt;/P&gt;
&lt;P&gt;is this the expected behaviour? Nothing is mentioned in the documentation&amp;nbsp;&lt;BR /&gt;&lt;A href="https://docs.paloaltonetworks.com/globalprotect/10-1/globalprotect-admin/globalprotect-gateways/configure-a-globalprotect-gateway" target="_blank"&gt;https://docs.paloaltonetworks.com/globalprotect/10-1/globalprotect-admin/globalprotect-gateways/configure-a-globalprotect-gateway&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;many thanks&lt;/P&gt;</description>
    <pubDate>Tue, 25 Apr 2023 08:29:09 GMT</pubDate>
    <dc:creator>JoseCortijo</dc:creator>
    <dc:date>2023-04-25T08:29:09Z</dc:date>
    <item>
      <title>Several client authentication in a Gateway</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/several-client-authentication-in-a-gateway/m-p/540032#M3975</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;we have a PA-850 running 10.1.8 firmware.&lt;/P&gt;
&lt;P&gt;We currently use GlobalProtect VPN using Symantec VIP authentication via RADIUS.&lt;/P&gt;
&lt;P&gt;We want to progressively migrate the authentication to Azure AD MFA (already synced with all accounts). I was wondering if I could simply add the new client authentication to the list and use it as a fall back authentication method.&lt;/P&gt;
&lt;P&gt;My approach was to remove user accounts one by one from Symantec Database. Then, the user opens global protect which first tries to authenticate against Symantec and after the failure falls back to Azure AD.&lt;/P&gt;
&lt;P&gt;is this the expected behaviour? Nothing is mentioned in the documentation&amp;nbsp;&lt;BR /&gt;&lt;A href="https://docs.paloaltonetworks.com/globalprotect/10-1/globalprotect-admin/globalprotect-gateways/configure-a-globalprotect-gateway" target="_blank"&gt;https://docs.paloaltonetworks.com/globalprotect/10-1/globalprotect-admin/globalprotect-gateways/configure-a-globalprotect-gateway&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;many thanks&lt;/P&gt;</description>
      <pubDate>Tue, 25 Apr 2023 08:29:09 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/several-client-authentication-in-a-gateway/m-p/540032#M3975</guid>
      <dc:creator>JoseCortijo</dc:creator>
      <dc:date>2023-04-25T08:29:09Z</dc:date>
    </item>
  </channel>
</rss>

