This is a straight port of the previous AD LDS provider for SharePoint Foundation 2010. This provider allows SharePoint Foundation administrators to connect to an LDAP-based directory service.
Please review the documentation page for this project. It can be downloaded here. Installation has changed from a manual installation to an MSI that will automatically install the DLL for you in the GAC.
Please report any bugs or issues in the discussions page. Feedback is also highly welcome!
SharePoint Foundation 2013 ships with the dll that provides the Microsoft.Office.Server.Security.LdapMembershipProvider and Microsoft.Office.Server.Security.LdapRoleProvider classes. Yay! Right? Let’s find out…
When properly configured for LDAP, be that Active Directory, AD LDS, OpenLDAP, and so forth, we start seeing these really weird errors in the ULS log in addition to getting a general error in SharePoint when we attempt to hit a Web Application configured for FBA using Microsoft’s provider.
|
1 2 3 4 5 6 |
SharePoint Foundation General 8nca Medium Application error when access /, Error=Common Language Runtime detected an invalid program. at Microsoft.Office.Server.Security.LdapMembershipProvider.get_Name() at System.Configuration.Provider.ProviderCollection.Add(ProviderBase provider) at System.Web.Configuration.ProvidersHelper.InstantiateProviders(ProviderSettingsCollection configProviders, ProviderCollection providers, Type providerType) at System.Web.Security.Membership.InitializeSettings(Boolean initializeGeneralSettings, RuntimeConfig appConfig, MembershipSection settings) at System.Web.Security.Membership.Initialize() at System.Web.Security.Membership.get_Provider() at Microsoft.SharePoint.ApplicationRuntime.SPHeaderManager.AddIsapiHeaders(HttpContext context, String encodedUrl, NameValueCollection hea... 786e149c-2433-409e-efe3-4cbff17c1f9f SharePoint Foundation General 8nca Medium ...ders) at Microsoft.SharePoint.ApplicationRuntime.SPRequestModule.PreRequestExecuteAppHandler(Object oSender, EventArgs ea) at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) 786e149c-2433-409e-efe3-4cbff17c1f9f SharePoint Foundation Runtime tkau Unexpected System.InvalidProgramException: Common Language Runtime detected an invalid program. at Microsoft.Office.Server.Security.LdapMembershipProvider.get_Name() at System.Configuration.Provider.ProviderCollection.Add(ProviderBase provider) at System.Web.Configuration.ProvidersHelper.InstantiateProviders(ProviderSettingsCollection configProviders, ProviderCollection providers, Type providerType) at System.Web.Security.Membership.InitializeSettings(Boolean initializeGeneralSettings, RuntimeConfig appConfig, MembershipSection settings) at System.Web.Security.Membership.Initialize() at System.Web.Security.Membership.get_Provider() at Microsoft.SharePoint.ApplicationRuntime.SPHeaderManager.AddIsapiHeaders(HttpContext context, String encodedUrl, NameValueCollection headers) ... 786e149c-2433-409e-efe3-4cbff17c1f9f SharePoint Foundation Runtime tkau Unexpected ... at Microsoft.SharePoint.ApplicationRuntime.SPRequestModule.PreRequestExecuteAppHandler(Object oSender, EventArgs ea) at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) 786e149c-2433-409e-efe3-4cbff17c1f9f SharePoint Foundation General ajlz0 High Getting Error Message for Exception System.InvalidProgramException: Common Language Runtime detected an invalid program. at Microsoft.Office.Server.Security.LdapMembershipProvider.get_Name() at System.Configuration.Provider.ProviderCollection.Add(ProviderBase provider) at System.Web.Configuration.ProvidersHelper.InstantiateProviders(ProviderSettingsCollection configProviders, ProviderCollection providers, Type providerType) at System.Web.Security.Membership.InitializeSettings(Boolean initializeGeneralSettings, RuntimeConfig appConfig, MembershipSection settings) at System.Web.Security.Membership.Initialize() at System.Web.Security.Membership.get_Provider() at Microsoft.SharePoint.ApplicationRuntime.SPHeaderManager.AddIsapiHeaders(HttpContext context, String enco... 786e149c-2433-409e-efe3-4cbff17c1f9f SharePoint Foundation General ajlz0 High ...dedUrl, NameValueCollection headers) at Microsoft.SharePoint.ApplicationRuntime.SPRequestModule.PreRequestExecuteAppHandler(Object oSender, EventArgs ea) at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) 786e149c-2433-409e-efe3-4cbff17c1f9f |
In addition, there is an ASP.NET Warning in the Application Event Log with an identical error. Why would we be getting an error of “Common Language Runtime detected an invalid program”? Well, glad you asked!
When your LdapMembershipProvider class looks like this…
…It is no wonder we get that error. Microsoft has specifically stripped out the code within the methods that provide the logic behind the Microsoft.Office.Server.Security.LdapMembershipProvider and LdapRoleProvider!
What does this mean to you? It means you have to build an alternate provider. I do have a provider for SharePoint Foundation 2010 that mimics the Microsoft provider, however the source needs to have it’s reference updated to for SharePoint 2013 (Microsoft.SharePoint.dll) and simply recompiled.
In addition to previous improvements found in 1.5 beta, Nauplius.ADLDS.FBA 1.6 for AD LDS configuration and User Profile import now supports non-Default zones! Other improvements include moving the Security Token Service timer job and health check rule to an Application Server package as well as leveraging the Lists web service. Lots of other minor fixes!
Please see the project’s Documentation. Any Discussions or Bugs are welcome!
Project main page – SharePoint AD LDS/ADAM
I’m releasing a beta of my AD LDS project that now incorporates the old Nauplius AD LDS User Profile Import as well as the alpha Nauplius.ADLDS.FBA project.
The new Nauplius.ADLDS.FBA 1.5 solution allows the administrator to easily provision an AD LDS provider against a Web Application, keeping all web.configs required consistent across the farm. In addition, the solution will pull in key User Profile properties from the configured AD LDS instance into the User Profile Service.
Please see the project’s Documentation. Any Discussions or Bugs are welcome!
Project main page – SharePoint AD LDS/ADAM