MSAD change (Microsoft 2020 Jan release)

Hi,

I came across the following Microsoft LDAP change that will be introduced in January 2020 and I was wondering if there is anything to bear in mind from an Anaplan point of view? (eg login, integration, etc).

Here is the link : https://support.microsoft.com/en-us/help/4520412/2020-ldap-channel-binding-and-ldap-signing-requirement-for-windows

Thanks,
Alessio

Accepted answers

All comments

usman.zia

Hi @Alessio_Pagliano,

Great point you've raised here!

Do you have an idea of the current requirements / functionality where these changes may have an impact?

When other providers change their systems / platforms it is always very important to consider the impact to our current anapan ecosystems!

Very important to stay up to date and tackle issues as soon as we see them!

Thanks,

Usman

sowim

Hallo Allesio,

I am Anastasios from Cyber Security Department. Thank you for highlighting this. The vulnerability is not related to office Add inn and we are expecting to patch internal systems on January 2020 according to the Microsoft's official plan of migration.

Thank you

Anastasios

anastasios_gkou

I confirm this as my reply!

Quick Links

Can you help?

Unanswered questions

How can i export accuracy metrics from Anaplan Forecaster to Model.
There was an error rendering this rich post.
How to use Client ID and Client Secret for API request directly?
Hi all, The Client ID and Client Secret are available, intended for uploading and downloading files. Could anyone advise how to use these credentials DIRECTLY to make API requests? Thank you!
New UX Filtering for Hierarchy sibling
I have A6 as the parent list and two sibling lists: A6.5 and A7. The A7 list includes an attribute that maps to A6.5. In the UX, the user will select A6.5 using a content selector, and the grid (dimensioned by A7) should display only the A7 items associated with that selected A6.5. Since the selector is a page context and…