<?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: Using LDAP groups with GlobalProtect in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/using-ldap-groups-with-globalprotect/m-p/318294#M81736</link>
    <description>&lt;P&gt;Panorama 8.1.13&lt;/P&gt;&lt;P&gt;PanOS 8.1.9-h4 on the Portal&lt;/P&gt;&lt;P&gt;PanOS 8.1.13 on the Gateways&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Using OpenLDAP on the directory servers, so the LDAP config uses "other".&lt;/P&gt;</description>
    <pubDate>Tue, 24 Mar 2020 18:07:47 GMT</pubDate>
    <dc:creator>fjwcash</dc:creator>
    <dc:date>2020-03-24T18:07:47Z</dc:date>
    <item>
      <title>Using LDAP groups with GlobalProtect</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/using-ldap-groups-with-globalprotect/m-p/318279#M81734</link>
      <description>&lt;P&gt;What's the magic incantation needed to use LDAP groups in the GlobalProtect Portal user/group list?&amp;nbsp; Instead of listing all umpteen dozen individual users.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a working GP Portal and multiple Gateway setup, using LDAP for authentication.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a working Group Mapping setup using groups from LDAP.&amp;nbsp; I can use "show user group list" and see all my LDAP groups.&amp;nbsp; I can use "show user group name mydomain\mygroup" (the shortname for it) to view all the members of the group.&amp;nbsp; And I can run "show user user-ids match-user myuser" to see which group(s) a user is in.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In the Portal config, I can add individual users to the user/group list for each individual Gateway.&amp;nbsp; But, with the number of VPN users increasing the past couple of weeks, it's getting cumbersome to edit the config, commit to Panorama, and push tot he firewalls.&amp;nbsp; Would be much nicer to just put an LDAP group in here, and update the member list in LDAP instead.&amp;nbsp; I just can't make this work!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If I remove a test user from the Portal config, and replace it with an LDAP group (which that test user is a member of), then I get "Not authorized to access GlobalProtect Portal".&amp;nbsp; Tried the shortname for the group, mydomain\shortname, and the full cn=mygroup,ou=groups... syntax.&amp;nbsp; Same result for each.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What am I missing?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Edit:&amp;nbsp; This is on Panorama 8.1.13, PanOS 8.1.9-h4 on the Portal, 8.1.13 on the Gateways.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Edit2: Further troubleshooting, running "test authentication" from the CLI on the portal and the gateway succeeds.&amp;nbsp; But, we already knew the LDAP config worked; it's trying to use the LDAP group on the Portal Config that's failing.&amp;nbsp; And there doesn't appear to be a way to test that at the CLI, or to get better logs.&lt;/P&gt;</description>
      <pubDate>Tue, 24 Mar 2020 19:10:04 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/using-ldap-groups-with-globalprotect/m-p/318279#M81734</guid>
      <dc:creator>fjwcash</dc:creator>
      <dc:date>2020-03-24T19:10:04Z</dc:date>
    </item>
    <item>
      <title>Re: Using LDAP groups with GlobalProtect</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/using-ldap-groups-with-globalprotect/m-p/318283#M81735</link>
      <description>&lt;P&gt;What version of PAN-OS are you running. There are some versions that had a bug when using a scoped LDAP group.&lt;/P&gt;</description>
      <pubDate>Tue, 24 Mar 2020 17:37:28 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/using-ldap-groups-with-globalprotect/m-p/318283#M81735</guid>
      <dc:creator>VincentPresogna</dc:creator>
      <dc:date>2020-03-24T17:37:28Z</dc:date>
    </item>
    <item>
      <title>Re: Using LDAP groups with GlobalProtect</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/using-ldap-groups-with-globalprotect/m-p/318294#M81736</link>
      <description>&lt;P&gt;Panorama 8.1.13&lt;/P&gt;&lt;P&gt;PanOS 8.1.9-h4 on the Portal&lt;/P&gt;&lt;P&gt;PanOS 8.1.13 on the Gateways&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Using OpenLDAP on the directory servers, so the LDAP config uses "other".&lt;/P&gt;</description>
      <pubDate>Tue, 24 Mar 2020 18:07:47 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/using-ldap-groups-with-globalprotect/m-p/318294#M81736</guid>
      <dc:creator>fjwcash</dc:creator>
      <dc:date>2020-03-24T18:07:47Z</dc:date>
    </item>
    <item>
      <title>Re: Using LDAP groups with GlobalProtect</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/using-ldap-groups-with-globalprotect/m-p/318295#M81737</link>
      <description>&lt;P&gt;Sorry, I can't help with this. I have been running 9.0 versions, wasn't until 9.0.5 that it was fixed. I am also doing LDAP auth against active directory.&lt;/P&gt;</description>
      <pubDate>Tue, 24 Mar 2020 18:09:47 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/using-ldap-groups-with-globalprotect/m-p/318295#M81737</guid>
      <dc:creator>VincentPresogna</dc:creator>
      <dc:date>2020-03-24T18:09:47Z</dc:date>
    </item>
    <item>
      <title>Re: Using LDAP groups with GlobalProtect</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/using-ldap-groups-with-globalprotect/m-p/319111#M81870</link>
      <description>&lt;P&gt;&lt;FONT color="#000000"&gt;Aha! Got it to work with the help of Palo Alto support.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;With OpenLDAP, you have to match the Domain Name in the LDAP Server Profile, the Authentication Profile, and the Group Mapping (and it doesn't like . in the domain).&amp;nbsp; We had it matched across them all, but using sub.sub.tld for the domain, which it doesn't like.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;And, in the Portal config, when you list the group, you have to use the full LDAP cn=groupname,ou=users,dc=sub,dc=sub,dc=tld.&amp;nbsp; It doesn't like using the domain\groupname short-name format.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;With those two settings changed, listsing just the group in the Portal config allows users in that group in LDAP to login!&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 27 Mar 2020 21:38:56 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/using-ldap-groups-with-globalprotect/m-p/319111#M81870</guid>
      <dc:creator>fjwcash</dc:creator>
      <dc:date>2020-03-27T21:38:56Z</dc:date>
    </item>
  </channel>
</rss>

