March 2020 Updates from Microsoft (LDAP specifically) and the Impact on FNMS

[kyle_wolff]

I'm looking for a consolidated list of areas Flexera FNMS customers would need to be aware of and/or double check based on the LDAP channel binding and LDAP signing requirement updates coming from Microsoft in March.

• https://support.microsoft.com/en-us/help/4520412/2020-ldap-channel-binding-and-ldap-signing-requirement-for-windows
• https://portal.msrc.microsoft.com/en-us/security-guidance/advisory/ADV190023

[ChrisG]

I would be looking at:

* AD connections configured in beacon(s)
* AD connections configured in business adapters

There may be other places to check, but I can't think of any at the moment.

[Tooling42]

Hi,

on one beacon server I found an ADImport.log which failed:

2020-02-19 00:00:33,791 [irectoryImport.Program] [INFO ] Active directory "Current domain" found in config.
2020-02-19 00:00:34,041 [rt.DomainDetailsImport] [ERROR] Failed to get defaultNamingContext from connection: LDAP:///RootDSE/
System.Security.Authentication.AuthenticationException: The user name or password is incorrect.

Can the March 2020 Updates the reason? Because it was working in past.