[HC to BCC, adding later response]
Hi Metze,
I will file a request to update the documentation and follow up.
Thank you for letting us know.
Best regards,
Jeff McCashland (He/him) | Senior Escalation Engineer | Microsoft Protocol Open
Specifications Team
Phone: +1 (425) 703-8300 x38300 |
[BCC protocol team]
Hi Metze
I BCC Windows Protocol team in this email thread. Whoever, take the case can
consider submitting a TDI to update the documentation.
"Ok, I've looked at the openldap code and found out that I have to prefix this
with "tls-server-end-point:".
With that I got it
[bcc dochelp]
Hi Metze
Thank you for contacting Protocol Support. We created SR Case -
TrackingID#2309280040006657 to track the issue.
Please do leave this tag - TrackingID#2309280040006657 in the subject for
future reference.
One our engineers will be contacting you shortly.
Hung-Chun Yu
Am 28.09.23 um 16:19 schrieb Stefan Metzmacher via cifs-protocol:
Hi DocHelp,
I'm trying to connect to a server with LdapEnforceChannelBinding=2
and can't get it working.
MS-NLMP specifies ClientChannelBindingsUnhashed and
ServerChannelBindingsUnhashed
as input from the application.
MS-ADTS
Hi DocHelp,
I'm trying to connect to a server with LdapEnforceChannelBinding=2
and can't get it working.
MS-NLMP specifies ClientChannelBindingsUnhashed and
ServerChannelBindingsUnhashed
as input from the application.
MS-ADTS 5.1.2.2 Using SSL/TLS specifies that "tls-server-endpoint"
channel
