<?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: ASA &amp; LDAP Authorization in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-ldap-authorization/m-p/706780#M422817</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I just created an LDAP server entry, put in my Base DN, used 'uid' as my Naming Attribute, and applied the LDAP attribute Map.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The LDAP attribute map contains:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Map Name: 'uid' as Customer Name, and 'cVPN-3000-IETF-Radius-Class' as the Cisco Name. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Map Value: 'johndoe' as Customer Value, and a group policy for the Cisco Value.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mark &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 07 Mar 2007 20:24:57 GMT</pubDate>
    <dc:creator>markbialik</dc:creator>
    <dc:date>2007-03-07T20:24:57Z</dc:date>
    <item>
      <title>ASA &amp; LDAP Authorization</title>
      <link>https://community.cisco.com/t5/network-security/asa-ldap-authorization/m-p/706778#M422815</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>Fri, 21 Feb 2020 09:17:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-ldap-authorization/m-p/706778#M422815</guid>
      <dc:creator>markbialik</dc:creator>
      <dc:date>2020-02-21T09:17:03Z</dc:date>
    </item>
    <item>
      <title>Re: ASA &amp; LDAP Authorization</title>
      <link>https://community.cisco.com/t5/network-security/asa-ldap-authorization/m-p/706779#M422816</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Authorization works if the object class cVPN-3000-User-Authorization is added to the schema.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How did you get Authentication working?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 05 Feb 2007 18:31:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-ldap-authorization/m-p/706779#M422816</guid>
      <dc:creator>bmeyercan</dc:creator>
      <dc:date>2007-02-05T18:31:03Z</dc:date>
    </item>
    <item>
      <title>Re: ASA &amp; LDAP Authorization</title>
      <link>https://community.cisco.com/t5/network-security/asa-ldap-authorization/m-p/706780#M422817</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I just created an LDAP server entry, put in my Base DN, used 'uid' as my Naming Attribute, and applied the LDAP attribute Map.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The LDAP attribute map contains:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Map Name: 'uid' as Customer Name, and 'cVPN-3000-IETF-Radius-Class' as the Cisco Name. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Map Value: 'johndoe' as Customer Value, and a group policy for the Cisco Value.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mark &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 07 Mar 2007 20:24:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-ldap-authorization/m-p/706780#M422817</guid>
      <dc:creator>markbialik</dc:creator>
      <dc:date>2007-03-07T20:24:57Z</dc:date>
    </item>
  </channel>
</rss>

