<?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 ACS 5.2 ldap authorization issue in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/acs-5-2-ldap-authorization-issue/m-p/2147518#M137794</link>
    <description>&lt;P&gt;Dear,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have users using a GPRS connection authenticating against ACS : &lt;/P&gt;&lt;P&gt;Fields received in radius package : Username &amp;amp; Calling-line_id&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have an ldap directory containing the same 2 fields : userPrincipalName &amp;amp; TelephoneNumber&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1)Is it possible to match the 2 fields received in the radius package against the 2 fields in LDAP, and based&lt;/P&gt;&lt;P&gt;on that granting/denying access ? (some sort of mulitple key).&lt;/P&gt;&lt;P&gt;2)Is it possible to match the calling-line-id against an ldap attribute (authorization section) ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The issue is that we have 3000+ GPRS users, and creating 3000+ entries in the end user filter is not&lt;/P&gt;&lt;P&gt;really an option.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Many thanks,&lt;/P&gt;&lt;P&gt;Lieven Stubbe&lt;/P&gt;&lt;P&gt;Belgian Railways&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 03:14:49 GMT</pubDate>
    <dc:creator>lni1</dc:creator>
    <dc:date>2019-03-11T03:14:49Z</dc:date>
    <item>
      <title>ACS 5.2 ldap authorization issue</title>
      <link>https://community.cisco.com/t5/network-access-control/acs-5-2-ldap-authorization-issue/m-p/2147518#M137794</link>
      <description>&lt;P&gt;Dear,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have users using a GPRS connection authenticating against ACS : &lt;/P&gt;&lt;P&gt;Fields received in radius package : Username &amp;amp; Calling-line_id&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have an ldap directory containing the same 2 fields : userPrincipalName &amp;amp; TelephoneNumber&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1)Is it possible to match the 2 fields received in the radius package against the 2 fields in LDAP, and based&lt;/P&gt;&lt;P&gt;on that granting/denying access ? (some sort of mulitple key).&lt;/P&gt;&lt;P&gt;2)Is it possible to match the calling-line-id against an ldap attribute (authorization section) ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The issue is that we have 3000+ GPRS users, and creating 3000+ entries in the end user filter is not&lt;/P&gt;&lt;P&gt;really an option.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Many thanks,&lt;/P&gt;&lt;P&gt;Lieven Stubbe&lt;/P&gt;&lt;P&gt;Belgian Railways&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 03:14:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/acs-5-2-ldap-authorization-issue/m-p/2147518#M137794</guid>
      <dc:creator>lni1</dc:creator>
      <dc:date>2019-03-11T03:14:49Z</dc:date>
    </item>
    <item>
      <title>ACS 5.2 ldap authorization issue</title>
      <link>https://community.cisco.com/t5/network-access-control/acs-5-2-ldap-authorization-issue/m-p/2147519#M137797</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;On second question; it is possible to match the calling-line-id against an ldap attribute (authorization section)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This requries an attribute-to-attribute comparison capability that is availabe in ACS release 5.3 on higher. If decide to upgrade I would recommend to upgrade to ACS 5.4&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Mar 2013 09:14:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/acs-5-2-ldap-authorization-issue/m-p/2147519#M137797</guid>
      <dc:creator>jrabinow</dc:creator>
      <dc:date>2013-03-29T09:14:48Z</dc:date>
    </item>
  </channel>
</rss>

