<?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: GlobalProtect Azure Saml user/group attribute Mapping in GlobalProtect Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/globalprotect-azure-saml-user-group-attribute-mapping/m-p/749062#M6167</link>
    <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/43480"&gt;@BPry&lt;/a&gt; ,&lt;/P&gt;
&lt;P&gt;Thanks for the reply , It is still unclear how the GP will distinguish which usergroup gets which VPN pool range with a single authentication profile that includes the usergroups (derived from Azure saml) in the allow list..&lt;BR /&gt;My aim is to make sure each usergroup fetched from Azure SAML is assigned with a specific set of vpn pool range , and with that a security rule can be configured to allow specific destination access based on the vpn pool ranges.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 27 Nov 2024 09:39:48 GMT</pubDate>
    <dc:creator>l2-security</dc:creator>
    <dc:date>2024-11-27T09:39:48Z</dc:date>
    <item>
      <title>GlobalProtect Azure Saml user/group attribute Mapping</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/globalprotect-azure-saml-user-group-attribute-mapping/m-p/703886#M6161</link>
      <description>&lt;P&gt;Hi Support,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am trying to configure Globalprotect with Azure Saml integration.&lt;/P&gt;
&lt;P&gt;The authentication part is configured following the link (&amp;nbsp;&lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g0000008U48CAE" target="_blank" rel="noopener"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g0000008U48CAE&lt;/A&gt;).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Additionally usergroup in Azure are configured with the attribute "group"&amp;nbsp; and is mapped to each usergroup name.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Saml authentication profile in PA firewall contains the user group attribute name as "group" (matching the usergroup attribute from Azure).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Now the question here is , do i need to create multiple Saml authentication profiles like one for the GP Portal authentication which contains the Allow list as "all",&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;And one each for every user group with their respective&amp;nbsp;&lt;SPAN&gt;Asserted&lt;/SPAN&gt; Azure user group name&amp;nbsp;in Allow list. which can be called in GP Gateway authentication configuration to map the usergroup with their vpn pool and other settings.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 26 Nov 2024 13:11:44 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/globalprotect-azure-saml-user-group-attribute-mapping/m-p/703886#M6161</guid>
      <dc:creator>l2-security</dc:creator>
      <dc:date>2024-11-26T13:11:44Z</dc:date>
    </item>
    <item>
      <title>Re: GlobalProtect Azure Saml user/group attribute Mapping</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/globalprotect-azure-saml-user-group-attribute-mapping/m-p/704805#M6164</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/275614"&gt;@l2-security&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;If I understand the question properly, you should be able to just have a single profile. You can utilize the user group on the portal and the gateway to control the configuration that each group receives or whether they're able to utilize that portal/gateway. So the authentication will use the single authentication profile while the actual portal agent configuration can be driven by the group alongside the gateways client settings.&lt;/P&gt;</description>
      <pubDate>Wed, 27 Nov 2024 01:49:01 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/globalprotect-azure-saml-user-group-attribute-mapping/m-p/704805#M6164</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2024-11-27T01:49:01Z</dc:date>
    </item>
    <item>
      <title>Re: GlobalProtect Azure Saml user/group attribute Mapping</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/globalprotect-azure-saml-user-group-attribute-mapping/m-p/749062#M6167</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/43480"&gt;@BPry&lt;/a&gt; ,&lt;/P&gt;
&lt;P&gt;Thanks for the reply , It is still unclear how the GP will distinguish which usergroup gets which VPN pool range with a single authentication profile that includes the usergroups (derived from Azure saml) in the allow list..&lt;BR /&gt;My aim is to make sure each usergroup fetched from Azure SAML is assigned with a specific set of vpn pool range , and with that a security rule can be configured to allow specific destination access based on the vpn pool ranges.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 27 Nov 2024 09:39:48 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/globalprotect-azure-saml-user-group-attribute-mapping/m-p/749062#M6167</guid>
      <dc:creator>l2-security</dc:creator>
      <dc:date>2024-11-27T09:39:48Z</dc:date>
    </item>
    <item>
      <title>Re: GlobalProtect Azure Saml user/group attribute Mapping</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/globalprotect-azure-saml-user-group-attribute-mapping/m-p/1238298#M7034</link>
      <description>&lt;P&gt;Did you manage to fix it? I am also trying to figure out how the Palo Identifies which On Premise AD group (azure synced) the user belongs to so it can match a config criteria selection and receive different VPN IP pools and also a different connect method.&lt;/P&gt;</description>
      <pubDate>Thu, 18 Sep 2025 09:10:53 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/globalprotect-azure-saml-user-group-attribute-mapping/m-p/1238298#M7034</guid>
      <dc:creator>nicoleannep</dc:creator>
      <dc:date>2025-09-18T09:10:53Z</dc:date>
    </item>
  </channel>
</rss>

