<?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 Active Directory in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/active-directory/m-p/3497680#M536636</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am requesting a feature enhancement to ISE 2.1:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are currently using Active Directory as an external identity source, however, all queries are over default TCP/389. We would like to continue using Active Directory as the external identity source, but over the secure LDAP, TCP/636&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is this possible? There is an external identity source available for LDAPS, but carries additional administration overhead. The Active Directory plugin integrates well.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 30 Dec 2016 15:41:20 GMT</pubDate>
    <dc:creator>anthony.munro</dc:creator>
    <dc:date>2016-12-30T15:41:20Z</dc:date>
    <item>
      <title>Active Directory</title>
      <link>https://community.cisco.com/t5/network-access-control/active-directory/m-p/3497680#M536636</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am requesting a feature enhancement to ISE 2.1:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are currently using Active Directory as an external identity source, however, all queries are over default TCP/389. We would like to continue using Active Directory as the external identity source, but over the secure LDAP, TCP/636&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is this possible? There is an external identity source available for LDAPS, but carries additional administration overhead. The Active Directory plugin integrates well.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 30 Dec 2016 15:41:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/active-directory/m-p/3497680#M536636</guid>
      <dc:creator>anthony.munro</dc:creator>
      <dc:date>2016-12-30T15:41:20Z</dc:date>
    </item>
    <item>
      <title>Re: Active Directory</title>
      <link>https://community.cisco.com/t5/network-access-control/active-directory/m-p/3497681#M536637</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;When ISE communicates with Microsoft Active Directory using ISE AD runtime agent (via AD join points), it encrypts the connections even though using TCP/389, and this is not configurable.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ISE may also connect to AD using LDAP protocol (via LDAP connector or LDAP ID source), where you have the option to use LDAPS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG alt="Screen Shot 2016-12-30 at 2.32.57 PM.png" class="image-1 jive-image" height="304" src="/legacyfs/online/fusion/103456_Screen Shot 2016-12-30 at 2.32.57 PM.png" style="height: 303.516px; width: 485px;" width="485" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 30 Dec 2016 22:34:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/active-directory/m-p/3497681#M536637</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2016-12-30T22:34:17Z</dc:date>
    </item>
  </channel>
</rss>

