Highlighted
Active participant

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

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.

Labels (1)
2 Replies
Highlighted
Community Manager Community Manager
Community Manager

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

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.
(Anything expressed here is my own view and not necessarily that of my employer, Flexera. If my reply answers a question you have raised, please click "ACCEPT AS SOLUTION".)
Highlighted
Active participant

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

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.

0 Kudos