Swopping out .Net Membership Provider (custom) with Active Directory

[Krokonoster]

Hi,

In my web application I created a custom implementation of the standard .net membership and role providers, using nHibernate. Works fine.

Now I have the requirement that client's should not only be able to host their own instance of my web application, but also be able to integrate with their own authentication system.

I know for a fact, they could write their own implementation of the membership and role providers and just make changes to the web.config. No biggie.

However, I believe many of these clients are using Active Directory.

Just wanted to confirm (note: never used AD) that in such case they can just as easily swop out the current providers with whatever one uses with AD, without any changes required to my web app?
(need to research, but right now I have to put that into a document whether possible or not and rather not lie by accident)

Thanks in advance

[rjv_rnjn]

Just wanted to confirm (note: never used AD) that in such case they can just as easily swop out the current providers with whatever one uses with AD, without any changes required to my web app?

This is possible but somebody has to write the concrete classes implementing the interface methods & properties for Active Directory. You should also look into the concept of Inversion of Control and see if it fits your scenario. I do not have much experience implementing that at this point of time but from the look of things seems could be useful in your case.

[Krokonoster]

Every app I create use IoC, don't worry about that. ;-)
Your answer is more trying to give me programming tips, not what I asked for but you hint in there (unless I got it wrong) that they can write a custom .net membership provider that implement AD.
If so, it's just a matter of modifying the web.config (telling the app to use this or that provider) which is exactly what I hope is possible.