AI OnAI Off
EPiServer 7 CMS Active Directory Membership Provider
Take a look at this blog post from Fredrik Haglund and first decide if you really want to use the LDAP based ActiveDirectoryMembershipProvider instead of the WindowsMembershipProvider. It also answers most of your questions.
http://blog.fredrikhaglund.se/blog/2010/03/08/episerver-security-and-access-control-12/
May 16, 2013 13:30
Great! If you use ActiveDirectoryMembershipProvider you usually want to inherit it and fix the wildcard problem described here:
Also when you have your own implementation you can easily add your own caching code to the methods of choice in order to reduce LDAP traffic.
May 17, 2013 9:33
For troubleshooting, feel free to check out
http://world.episerver.com/Blogs/Daniel-Ovaska/Dates/2013/2/How-to-solve-problems-with-the-ActiveDirectoryMembershipProvider-and-similar-ldap-integrations/
May 21, 2014 17:03
This thread is locked and should be used for reference only. Please use the Episerver CMS 7 and earlier versions forum to open new discussions.
Hi!
We are about to start a new project where the customer needs an Active Directory integration to EPiServer 7 CMS. I haven't worked with AD Membership Provider before and was wondering the following things:
* Does EPi CMS authenticate against AD with LDAP on each login?
* Does EPi CMS replicate the users to SQL Server Database or are the credentials just cached?
* What happens when the connection from the EPiServer to AD disconnects - will the authentication work if the cache is up and running?
* If you set the CacheExpiration to lets say 12 hours - does it mean that the cache will not be refreshed during this time or is it updated incrementally? i.e. The user changes the account password - does he need to wait till the cache is refreshed - in this case 12 hours in order to login with the new password?
* What is cached - only the users who have logged in or all the credentials that are under the defined membership provider location?
Cheers,