2020 LDAP channel binding and LDAP signing requirement for Windows

[Timothy F1]

Does ldap (non ldaps) integration using the Mid server work with ldap signing and channel binding? I'm asking because this will be mandatory soon and I couldn't find anywhere in the docs that it addressed it explicitly. 

2020 LDAP channel binding and LDAP signing requirement for Windows

https://support.microsoft.com/en-us/help/4520412/2020-ldap-channel-binding-and-ldap-signing-requirem...

[Timothy F1]

They didn't give me an exact date, just a ballpark of the next few weeks. I got the reply a few days ago. 

[Zoso1]

Using LDAP and mid servers, we were stuck on "not secure" connections, let's hope this KB brings more highlight on this.

In case this helps in the meantime here is how we set up the ldaps:

Once the domain controllers are set up to accept SSL, on the LDAP server record in ServiceNow, simply remove the mid server entry, check the SSL checkbox and set the URL pointing to your DC.

the URL has this format:

ldaps://yourFullDomainName:yourPort/

Note: there is a S to ldaps and the default port is 636

There is another turn around which consists in using some NAT

[Timothy F1 · Accepted solution]

ServiceNow posted instructions for dealing with the changes. They are listed here: https://hi.service-now.com/kb_view.do?sysparm_article=KB0793353

[Timothy F1]

@Michael Jones - CloudPires posted an excellent step-by-step guide for setting this up here https://community.servicenow.com/community?id=community_article&sys_id=a4ff5ed91bf64094fff162c4bd4bc...