<?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: Global protect username tags in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/global-protect-username-tags/m-p/195315#M58362</link>
    <description>&lt;P&gt;well.... yes and no, then yes again...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;you can use RSA groups but only for auth level. so you could allow RSA Grouped users to actually use the authentication profile.&lt;/P&gt;&lt;P&gt;this will not populate to policies. this requires LDAP based group membership.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;as a workaround...&amp;nbsp;&amp;nbsp; if you have an LDAP server or use AD you can create groups that serve no other use than group membership and reference these to the matched usernames within RSA.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;it may be that your users are already on AD, this will be a win win situation.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;please note that this "group membership" will only apply to the PA that GP authenticates to, it will not work if the users traverse any other firewall with such policies.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Mick.&lt;/P&gt;</description>
    <pubDate>Tue, 16 Jan 2018 15:32:20 GMT</pubDate>
    <dc:creator>Mick_Ball</dc:creator>
    <dc:date>2018-01-16T15:32:20Z</dc:date>
    <item>
      <title>Global protect username tags</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/global-protect-username-tags/m-p/195295#M58355</link>
      <description>&lt;P&gt;Hello all,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I use RADIUS server for authenticating GP users. Is there a possibility to read tags sent by RADIUS server associated with user groups and palo could allow/deny specific users?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 16 Jan 2018 13:33:01 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/global-protect-username-tags/m-p/195295#M58355</guid>
      <dc:creator>SThatipelly</dc:creator>
      <dc:date>2018-01-16T13:33:01Z</dc:date>
    </item>
    <item>
      <title>Re: Global protect username tags</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/global-protect-username-tags/m-p/195315#M58362</link>
      <description>&lt;P&gt;well.... yes and no, then yes again...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;you can use RSA groups but only for auth level. so you could allow RSA Grouped users to actually use the authentication profile.&lt;/P&gt;&lt;P&gt;this will not populate to policies. this requires LDAP based group membership.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;as a workaround...&amp;nbsp;&amp;nbsp; if you have an LDAP server or use AD you can create groups that serve no other use than group membership and reference these to the matched usernames within RSA.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;it may be that your users are already on AD, this will be a win win situation.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;please note that this "group membership" will only apply to the PA that GP authenticates to, it will not work if the users traverse any other firewall with such policies.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Mick.&lt;/P&gt;</description>
      <pubDate>Tue, 16 Jan 2018 15:32:20 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/global-protect-username-tags/m-p/195315#M58362</guid>
      <dc:creator>Mick_Ball</dc:creator>
      <dc:date>2018-01-16T15:32:20Z</dc:date>
    </item>
  </channel>
</rss>

