<?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 Microsoft AD as AAA server in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/microsoft-ad-as-aaa-server/m-p/544062#M427659</link>
    <description>&lt;P&gt;Is it possible to use  Microsift AD server , on inside   ( region ) of PIX as AAA server for packets exiting PIX and going   either to outside or to DMZ region.&lt;/P&gt;&lt;P&gt;highly appreciate  link on Cisco.com / Microsoft.com &lt;/P&gt;&lt;P&gt;Thanx&lt;/P&gt;</description>
    <pubDate>Sun, 10 Mar 2019 21:29:32 GMT</pubDate>
    <dc:creator>bapatsubodh</dc:creator>
    <dc:date>2019-03-10T21:29:32Z</dc:date>
    <item>
      <title>Microsoft AD as AAA server</title>
      <link>https://community.cisco.com/t5/network-access-control/microsoft-ad-as-aaa-server/m-p/544062#M427659</link>
      <description>&lt;P&gt;Is it possible to use  Microsift AD server , on inside   ( region ) of PIX as AAA server for packets exiting PIX and going   either to outside or to DMZ region.&lt;/P&gt;&lt;P&gt;highly appreciate  link on Cisco.com / Microsoft.com &lt;/P&gt;&lt;P&gt;Thanx&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 21:29:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/microsoft-ad-as-aaa-server/m-p/544062#M427659</guid>
      <dc:creator>bapatsubodh</dc:creator>
      <dc:date>2019-03-10T21:29:32Z</dc:date>
    </item>
    <item>
      <title>Re: Microsoft AD as AAA server</title>
      <link>https://community.cisco.com/t5/network-access-control/microsoft-ad-as-aaa-server/m-p/544063#M427661</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Some LDAP servers (including the Microsoft Active Directory server) require the security appliance to establish a handshake via authenticated binding before they accept requests for any other LDAP operations. The security appliance identifies itself for authenticated binding by attaching a Login DN field to the user authentication request. The Login DN field defines the authentication characteristics of the security appliance; these characteristics should correspond to those of a user with administration privileges&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 06 Mar 2006 17:22:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/microsoft-ad-as-aaa-server/m-p/544063#M427661</guid>
      <dc:creator>wong34539</dc:creator>
      <dc:date>2006-03-06T17:22:39Z</dc:date>
    </item>
  </channel>
</rss>

