<?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 ASA &amp; LDAP Authorization in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/asa-ldap-authorization/m-p/701279#M422532</link>
    <description>&lt;P&gt;Hello:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a LDAP server configured and authentication working just fine.  My next goal is to provide SSL VPN services to some employees.  Their Tunnel Group membership should depend upon their LDAP 'group' membership.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example, our LDAP administrator has configured user entries like this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;dn: uid=jdoe,ou=People,o=company.com&lt;/P&gt;&lt;P&gt;givenName: John&lt;/P&gt;&lt;P&gt;sn: Doe&lt;/P&gt;&lt;P&gt;mail: &lt;A href="mailto:jdoe@company.com" target="_blank"&gt;jdoe@company.com&lt;/A&gt;&lt;/P&gt;&lt;P&gt;objectClass: top&lt;/P&gt;&lt;P&gt;objectClass: person&lt;/P&gt;&lt;P&gt;objectClass: organizationalPerson&lt;/P&gt;&lt;P&gt;objectClass: inetOrgPerson&lt;/P&gt;&lt;P&gt;objectClass: inetorgpersonsub1&lt;/P&gt;&lt;P&gt;uid: jdoe&lt;/P&gt;&lt;P&gt;cn: John Doe&lt;/P&gt;&lt;P&gt;description: Employee&lt;/P&gt;&lt;P&gt;description: Information Systems&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;He seems to like to use 'description' instead of OU for some reason, but that's out of my control.  I assume I need to perform some sort of LDAP Attribute mapping to make this happen.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the above example, I would like to create a Tunnel Group called 'IS' on the ASA, and if a user has 'description: Information Systems' in the ir LDAP, they would be mapped to the 'IS' tunnel group.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can someone shed some light?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mark&lt;/P&gt;</description>
    <pubDate>Sun, 10 Mar 2019 21:49:26 GMT</pubDate>
    <dc:creator>markbialik</dc:creator>
    <dc:date>2019-03-10T21:49:26Z</dc:date>
    <item>
      <title>ASA &amp; LDAP Authorization</title>
      <link>https://community.cisco.com/t5/network-access-control/asa-ldap-authorization/m-p/701279#M422532</link>
      <description>&lt;P&gt;Hello:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a LDAP server configured and authentication working just fine.  My next goal is to provide SSL VPN services to some employees.  Their Tunnel Group membership should depend upon their LDAP 'group' membership.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example, our LDAP administrator has configured user entries like this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;dn: uid=jdoe,ou=People,o=company.com&lt;/P&gt;&lt;P&gt;givenName: John&lt;/P&gt;&lt;P&gt;sn: Doe&lt;/P&gt;&lt;P&gt;mail: &lt;A href="mailto:jdoe@company.com" target="_blank"&gt;jdoe@company.com&lt;/A&gt;&lt;/P&gt;&lt;P&gt;objectClass: top&lt;/P&gt;&lt;P&gt;objectClass: person&lt;/P&gt;&lt;P&gt;objectClass: organizationalPerson&lt;/P&gt;&lt;P&gt;objectClass: inetOrgPerson&lt;/P&gt;&lt;P&gt;objectClass: inetorgpersonsub1&lt;/P&gt;&lt;P&gt;uid: jdoe&lt;/P&gt;&lt;P&gt;cn: John Doe&lt;/P&gt;&lt;P&gt;description: Employee&lt;/P&gt;&lt;P&gt;description: Information Systems&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;He seems to like to use 'description' instead of OU for some reason, but that's out of my control.  I assume I need to perform some sort of LDAP Attribute mapping to make this happen.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the above example, I would like to create a Tunnel Group called 'IS' on the ASA, and if a user has 'description: Information Systems' in the ir LDAP, they would be mapped to the 'IS' tunnel group.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can someone shed some light?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mark&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 21:49:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/asa-ldap-authorization/m-p/701279#M422532</guid>
      <dc:creator>markbialik</dc:creator>
      <dc:date>2019-03-10T21:49:26Z</dc:date>
    </item>
    <item>
      <title>Re: ASA &amp; LDAP Authorization</title>
      <link>https://community.cisco.com/t5/network-access-control/asa-ldap-authorization/m-p/701280#M422534</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The SSL VPN Client (SVC) is a VPN tunneling technology that gives remote users the benefits of an IPSec VPN client without the need for network administrators to install and configure IPSec VPN clients on remote computers. REfer URL for SSL VPN Servies&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/products/ps6120/products_configuration_guide_chapter09186a0080565910.html" target="_blank"&gt;http://www.cisco.com/en/US/products/ps6120/products_configuration_guide_chapter09186a0080565910.html&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 08 Nov 2006 20:47:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/asa-ldap-authorization/m-p/701280#M422534</guid>
      <dc:creator>wong34539</dc:creator>
      <dc:date>2006-11-08T20:47:59Z</dc:date>
    </item>
  </channel>
</rss>

