Upgrade from LDAPCP Classic


LDAPCP Classic and LDAPCP Second Edition are 2 independent SharePoint solutions / claims providers. It is perfectly safe to run both on the same SharePoint farm: Installing/updating/removing one has no effect on the other.

See the announcement to know more about the reasons for this new claims provider.


LDAPCP SE and LDAPCP Classic each have their own configuration, and LDAPCP SE cannot import the configuration from LDAPCP Classic.

Differences between solutions

LDAPCP SE has higher requirements:

Minimum version required forLDAPCP SELDAPC Classic
.NET Framework.NET 4.8.NET 4.6.2
SharePoint version20162013

The table below highlights the notable differences in SharePoint:

Claims provider nameLDAPCPSELDAPCP
Product/Area in the logsLDAPCPSELDAPCP
SharePoint solution typeApplicationServerWebFrontEnd

Switch between claims providers

On a farm where both claims providers are istalled, it is very quick to switch from one to the other:

  • To enable LDAPCP SE:
$trust = Get-SPTrustedIdentityTokenIssuer "SPTRUST NAME"
$trust.ClaimProviderName = "LDAPCPSE"
  • To enable LDAPCP Classic:
$trust = Get-SPTrustedIdentityTokenIssuer "SPTRUST NAME"
$trust.ClaimProviderName = "LDAPCP"

Remove LDAPCP Classic

Once you are satisfied that LDAPCP SE runs well, you can safely uninstall LDAPCP Classic. This won’t have any impact on LDAPCP SE.