Some users may experience issues accessing the case portal. For more information, please click here.

This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Accept
Reject
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
kyle_wolff
Level 6
‎Feb 24, 2020 10:00 AM

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)
Labels

This thread has been automatically locked due to inactivity.

To continue the discussion, please start a new thread.
2 Replies
ChrisG
Community Manager Community Manager
Community Manager
‎Feb 24, 2020 03:23 PM

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.
(Did my reply solve the question? Click "ACCEPT AS SOLUTION" to help others find answers faster. Liked something? Click "KUDO". Anything expressed here is my own view and not necessarily that of my employer, Flexera.)
Tooling42
Level 7
In response to ChrisG
‎Feb 28, 2020 05:31 AM

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