A new claims provider - LDAPCP Second Edition

[Yvand]

On February 26, I released a major new version, that is the biggest update I ever made on this project since it started.
The changes are so big that I had to change the name of the claims provider, which is now LDAPCPSE.

The documentation has been updated in the project site.

Main improvements

• The SharePoint solution is now of type ApplicationServer, which both simplifies and improves the reliability of the install/update/remove operations.
• Administration pages were redesigned to be more intuitive while offering more customization.
• It supports using the SID attribute.
• It gets the nested groups when doing augmentation using LDAP queries.
• A huge amount of optimizations.

Overview of the changes in SharePoint

• A new solution name: LDAPCPSE.wsp
• A new claims provider: LDAPCPSE
• The minimum SharePoint version required is 2016
• The minimum .NET Framework required is 4.8
• It no longer works on SharePoint 2013

Why a new claims provider

LDAPCP (Classic) had too many early design flaws that I could not fix without making breaking changes.
But a (custom) claims provider is a very critical component in a SharePoint farm: An unexpected error when it runs can prevent users to sign-in and impact many services and features in SharePoint.
So the only safe way to make the redesign safe was to create a new claims provider, but of course it is a huge work I always postponed.

But LDAPCP has a twin: EntraCP! And I rewrote it entirely a few months ago.
So I reused most of this work on this new version of LDAPCP.
I started with EntraCP because it uses dependencies to connect to Graph, and those used before the rewrite were completely obsolete.