<?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: EAP-MSCHAPv2 support with AD using LDAP broker in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/eap-mschapv2-support-with-ad-using-ldap-broker/m-p/3605642#M517956</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This is the LDAP directory broker product &lt;A href="https://www.radiantlogic.com/products/radiantone-vds-standard-edition/" title="https://www.radiantlogic.com/products/radiantone-vds-standard-edition/"&gt;https://www.radiantlogic.com/products/radiantone-vds-standard-edition/&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 08 Feb 2018 16:47:06 GMT</pubDate>
    <dc:creator>mulatif</dc:creator>
    <dc:date>2018-02-08T16:47:06Z</dc:date>
    <item>
      <title>EAP-MSCHAPv2 support with AD using LDAP broker</title>
      <link>https://community.cisco.com/t5/network-access-control/eap-mschapv2-support-with-ad-using-ldap-broker/m-p/3605641#M517955</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;As per the below document (Page 12)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/security/ise/2-2/admin_guide/b_ise_admin_guide_22/b_ise_admin_guide_22_chapter_01101.pdf" style="font-size: 10pt;" title="https://www.cisco.com/c/en/us/td/docs/security/ise/2-2/admin_guide/b_ise_admin_guide_22/b_ise_admin_guide_22_chapter_01101.pdf"&gt;https://www.cisco.com/c/en/us/td/docs/security/ise/2-2/admin_guide/b_ise_admin_guide_22/b_ise_admin_guide_22_chapter_011…&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;EAP-MSCHAPv2 is supported with AD and not with LDAP.&lt;/P&gt;&lt;P&gt;However I have a customer, who are evaluating to do ISE and AD integration through a LDAP directory broker service (i.e. add AD as an LDAP Server) instead of the 'native join', which is the more common way to do it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the above case, does the supported authentication table is still applicable ? i.e. EAP-MSCHAPv2 is not going to be supported even though the back-end is still AD and only the join method has changed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Naman&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Feb 2018 16:44:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/eap-mschapv2-support-with-ad-using-ldap-broker/m-p/3605641#M517955</guid>
      <dc:creator>mulatif</dc:creator>
      <dc:date>2018-02-08T16:44:15Z</dc:date>
    </item>
    <item>
      <title>Re: EAP-MSCHAPv2 support with AD using LDAP broker</title>
      <link>https://community.cisco.com/t5/network-access-control/eap-mschapv2-support-with-ad-using-ldap-broker/m-p/3605642#M517956</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This is the LDAP directory broker product &lt;A href="https://www.radiantlogic.com/products/radiantone-vds-standard-edition/" title="https://www.radiantlogic.com/products/radiantone-vds-standard-edition/"&gt;https://www.radiantlogic.com/products/radiantone-vds-standard-edition/&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Feb 2018 16:47:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/eap-mschapv2-support-with-ad-using-ldap-broker/m-p/3605642#M517956</guid>
      <dc:creator>mulatif</dc:creator>
      <dc:date>2018-02-08T16:47:06Z</dc:date>
    </item>
    <item>
      <title>Re: EAP-MSCHAPv2 support with AD using LDAP broker</title>
      <link>https://community.cisco.com/t5/network-access-control/eap-mschapv2-support-with-ad-using-ldap-broker/m-p/3605643#M517957</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, the support table is applicable to any ID store configured as a LDAP ID source in ISE.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Feb 2018 16:53:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/eap-mschapv2-support-with-ad-using-ldap-broker/m-p/3605643#M517957</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2018-02-08T16:53:11Z</dc:date>
    </item>
  </channel>
</rss>

