<?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: LDAP connection failures when channel binding is enforced by the Windows LDAP server in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/LDAP-connection-failures-when-channel-binding-is-enforced-by-the-Windows-LDAP/m-p/161211#M36809</link>
    <description>&lt;P&gt;If you need this fixed, I would recommending talking to your account team. They can help prioritize this if needed if this is going to break things for you.&lt;/P&gt;</description>
    <pubDate>Mon, 16 Nov 2020 22:03:17 GMT</pubDate>
    <dc:creator>paul_stejskal</dc:creator>
    <dc:date>2020-11-16T22:03:17Z</dc:date>
    <item>
      <title>LDAP connection failures when channel binding is enforced by the Windows LDAP server</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/LDAP-connection-failures-when-channel-binding-is-enforced-by-the-Windows-LDAP/m-p/161187#M36805</link>
      <description>&lt;H5 class="editable"&gt;&lt;STRONG&gt;Change&amp;nbsp;1:&lt;/STRONG&gt;&lt;STRONG&gt;Use&amp;nbsp;the LdapEnforceChannelBinding registry entry to make LDAP authentication over SSL/TLS more secure &lt;/STRONG&gt;&amp;nbsp;&lt;/H5&gt;
&lt;UL&gt;
&lt;LI&gt;This option affects LDAP over TLS or LDAPS connections. &lt;STRONG&gt;The proposed Windows update for this setting should have no impact on ONTAP authentication. &amp;nbsp;&lt;/STRONG&gt;
&lt;UL&gt;
&lt;LI&gt;More information on &lt;A href="https://docs.netapp.com/ontap-9/topic/com.netapp.doc.cdot-famg-cifs/GUID-0E97E7F2-D46D-4883-B95B-A066B0D52B3D.html" target="_blank" rel="noreferrer noopener"&gt;LDAP over TLS concepts&lt;/A&gt; and&amp;nbsp;&lt;A title="Does ONTAP support port 636 for LDAPS (LDAP over SSL)" href="https://kb.netapp.com/Advice_and_Troubleshooting/Data_Storage_Software/ONTAP_OS/Does_ONTAP_support_port_636_for_LDAPS%3F" rel="internal" target="_blank"&gt;Does ONTAP support port 636 for LDAPS (LDAP over SSL)&lt;/A&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;LI&gt;Currently ONTAP does not support LDAP Channel Binding, this feature is being tracked here: &amp;nbsp;
&lt;UL&gt;
&lt;LI&gt;&lt;A href="https://mysupport.netapp.com/NOW/cgi-bin/bol?Type=Detail&amp;amp;Display=1136213" target="_blank" rel="noreferrer noopener"&gt;1136213 Implement channel binding tokens for LDAP with StartTLS &lt;/A&gt;&amp;nbsp;&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;Are there any progress on BUG 1136213 ?&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 10:45:30 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/LDAP-connection-failures-when-channel-binding-is-enforced-by-the-Windows-LDAP/m-p/161187#M36805</guid>
      <dc:creator>pal</dc:creator>
      <dc:date>2025-06-04T10:45:30Z</dc:date>
    </item>
    <item>
      <title>Re: LDAP connection failures when channel binding is enforced by the Windows LDAP server</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/LDAP-connection-failures-when-channel-binding-is-enforced-by-the-Windows-LDAP/m-p/161188#M36806</link>
      <description>&lt;P&gt;Well, per the bug if you really want to turn that feature on instead of setting to 2:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;Set "LdapEnforceChannelBinding" on the LDAP server to "1" which indicates "Enabled,
 when supported".&amp;nbsp;&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 16 Nov 2020 12:26:19 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/LDAP-connection-failures-when-channel-binding-is-enforced-by-the-Windows-LDAP/m-p/161188#M36806</guid>
      <dc:creator>TMACMD</dc:creator>
      <dc:date>2020-11-16T12:26:19Z</dc:date>
    </item>
    <item>
      <title>Re: LDAP connection failures when channel binding is enforced by the Windows LDAP server</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/LDAP-connection-failures-when-channel-binding-is-enforced-by-the-Windows-LDAP/m-p/161211#M36809</link>
      <description>&lt;P&gt;If you need this fixed, I would recommending talking to your account team. They can help prioritize this if needed if this is going to break things for you.&lt;/P&gt;</description>
      <pubDate>Mon, 16 Nov 2020 22:03:17 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/LDAP-connection-failures-when-channel-binding-is-enforced-by-the-Windows-LDAP/m-p/161211#M36809</guid>
      <dc:creator>paul_stejskal</dc:creator>
      <dc:date>2020-11-16T22:03:17Z</dc:date>
    </item>
    <item>
      <title>Re: LDAP connection failures when channel binding is enforced by the Windows LDAP server</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/LDAP-connection-failures-when-channel-binding-is-enforced-by-the-Windows-LDAP/m-p/161459#M36881</link>
      <description>&lt;P&gt;Hi Pal,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Our Engineering Team is working closely with Microsoft and has provided an update last week that the fix for&amp;nbsp;&lt;A href="https://mysupport.netapp.com/NOW/cgi-bin/bol?Type=Detail&amp;amp;Display=1136213" target="_self"&gt;RFE 1136213: Implement channel binding tokens for LDAP with StartTLS&lt;/A&gt;&amp;nbsp;is tentatively scheduled for ONTAP 9.10. As&amp;nbsp;paul_stejskal mentioned, please work with your Account Team if you need this fixed earlier.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Team NetApp&lt;/P&gt;</description>
      <pubDate>Tue, 24 Nov 2020 05:50:54 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/LDAP-connection-failures-when-channel-binding-is-enforced-by-the-Windows-LDAP/m-p/161459#M36881</guid>
      <dc:creator>ttran</dc:creator>
      <dc:date>2020-11-24T05:50:54Z</dc:date>
    </item>
  </channel>
</rss>

