Hello Daniel,
I have put my efforts to get ActiveDirectoryMembershipProvider working on hold, and am still hoping to be allowed to use the SQLMembershipProvider.
Here is what I wrote to my supervisor about my current situation with the AD provider:
- After a lot of frustration, I learned that one must use the default ports (389 and 636) to access AD LDS – unless one is willing to go through a lot of work. (See http://msdn.microsoft.com/en-us/library/system.web.security.activedirectorymembershipprovider.aspx in the ADAM Configuration section.) I had been attempting to use port 60000 and 60001 (for SSL).
- I currently have this membership provider set up on my dev server, and I can add users from AD LDS to SharePoint groups, etc. manually, but when trying to use the methods provided for creating and managing accounts, I ran into problems.
- One of them is described in the link above (in point 1). Here’s an excerpt, “The ActiveDirectoryMembershipProvider class requires unrestricted DirectoryServicesPermission permission to run.” This is from the Security Note in the Remarks section. I found this to be too complicated to do – especially to do with confidence that I have done it correctly and in a secure way. This is what caused me to give up, for now, on this solution.