<?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 LDAP query in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ldap-query/m-p/3451426#M522778</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have a customer having some issues with creating authorization policies based on LDAP attributes. See below:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="font-size: 11pt; font-family: Calibri, sans-serif;"&gt;They want to control MAB workstations network placement based on gidNumbers.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="font-size: 11pt; font-family: Calibri, sans-serif;"&gt;Two authorization policies defined with ISE for MAB:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="font-size: 11pt; font-family: Calibri, sans-serif;"&gt;rule 1 - Wired_MAB and ldap:ExternalGroups EQUALS 1000 then dacl_test&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="font-size: 11pt; font-family: Calibri, sans-serif;"&gt;rule 2 - Wired_MAB then dacl_no_gid&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="font-size: 11pt; font-family: Calibri, sans-serif;"&gt;Following device authentication via the LDAP and during the authorization phase devices matching rule #1 are skipping rule 1 and matching the simpler rule 2.&amp;nbsp; We want to control workstation placement based on gidNumber or some other ldap group membership or ldap attribute.&amp;nbsp; In this way, we can script ldapmodify to move workstations through various phases of our build and analysis both before and after users have done their work.&lt;/P&gt;&lt;P style="font-size: 11pt; font-family: Calibri, sans-serif;"&gt;&lt;/P&gt;&lt;P style="font-size: 11pt; font-family: Calibri, sans-serif;"&gt;Is there something missing in the policy? Is there a better way to accomplish matching on the gidNumber?&lt;/P&gt;&lt;P style="font-size: 11pt; font-family: Calibri, sans-serif;"&gt;&lt;/P&gt;&lt;P style="font-size: 11pt; font-family: Calibri, sans-serif;"&gt;Thanks&lt;/P&gt;&lt;P style="font-size: 11pt; font-family: Calibri, sans-serif;"&gt;&lt;/P&gt;&lt;P style="font-size: 11pt; font-family: Calibri, sans-serif;"&gt;- Paul&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 16 Aug 2017 18:37:18 GMT</pubDate>
    <dc:creator>pschnake</dc:creator>
    <dc:date>2017-08-16T18:37:18Z</dc:date>
    <item>
      <title>LDAP query</title>
      <link>https://community.cisco.com/t5/network-access-control/ldap-query/m-p/3451426#M522778</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have a customer having some issues with creating authorization policies based on LDAP attributes. See below:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="font-size: 11pt; font-family: Calibri, sans-serif;"&gt;They want to control MAB workstations network placement based on gidNumbers.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="font-size: 11pt; font-family: Calibri, sans-serif;"&gt;Two authorization policies defined with ISE for MAB:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="font-size: 11pt; font-family: Calibri, sans-serif;"&gt;rule 1 - Wired_MAB and ldap:ExternalGroups EQUALS 1000 then dacl_test&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="font-size: 11pt; font-family: Calibri, sans-serif;"&gt;rule 2 - Wired_MAB then dacl_no_gid&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="font-size: 11pt; font-family: Calibri, sans-serif;"&gt;Following device authentication via the LDAP and during the authorization phase devices matching rule #1 are skipping rule 1 and matching the simpler rule 2.&amp;nbsp; We want to control workstation placement based on gidNumber or some other ldap group membership or ldap attribute.&amp;nbsp; In this way, we can script ldapmodify to move workstations through various phases of our build and analysis both before and after users have done their work.&lt;/P&gt;&lt;P style="font-size: 11pt; font-family: Calibri, sans-serif;"&gt;&lt;/P&gt;&lt;P style="font-size: 11pt; font-family: Calibri, sans-serif;"&gt;Is there something missing in the policy? Is there a better way to accomplish matching on the gidNumber?&lt;/P&gt;&lt;P style="font-size: 11pt; font-family: Calibri, sans-serif;"&gt;&lt;/P&gt;&lt;P style="font-size: 11pt; font-family: Calibri, sans-serif;"&gt;Thanks&lt;/P&gt;&lt;P style="font-size: 11pt; font-family: Calibri, sans-serif;"&gt;&lt;/P&gt;&lt;P style="font-size: 11pt; font-family: Calibri, sans-serif;"&gt;- Paul&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 16 Aug 2017 18:37:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ldap-query/m-p/3451426#M522778</guid>
      <dc:creator>pschnake</dc:creator>
      <dc:date>2017-08-16T18:37:18Z</dc:date>
    </item>
    <item>
      <title>Re: LDAP query</title>
      <link>https://community.cisco.com/t5/network-access-control/ldap-query/m-p/3451427#M522779</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What version/Patch Level are you running on ISE?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You might try to write&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #3d3d3d; font-family: Calibri, sans-serif; font-size: 14.6667px;"&gt;rule 1 - ldap:ExternalGroups EQUALS 1000 and &lt;SPAN style="color: #3d3d3d; font-family: Calibri, sans-serif; font-size: 14.6667px;"&gt;Wired_MAB &lt;/SPAN&gt;then dacl_test&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Aug 2017 12:41:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ldap-query/m-p/3451427#M522779</guid>
      <dc:creator>Charlie Moreton</dc:creator>
      <dc:date>2017-08-17T12:41:53Z</dc:date>
    </item>
    <item>
      <title>Re: LDAP query</title>
      <link>https://community.cisco.com/t5/network-access-control/ldap-query/m-p/3451428#M522780</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks. They are running 2.2 but not sure of the patch level. And, the customer figured it out. He was able to fix the ldap gid issue by using the gid as an attribute rather than trying to match the gid from the group.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Aug 2017 14:31:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ldap-query/m-p/3451428#M522780</guid>
      <dc:creator>pschnake</dc:creator>
      <dc:date>2017-08-17T14:31:43Z</dc:date>
    </item>
  </channel>
</rss>

