Having read nearly every post about AD and DNN over the past couple of years or so, I find it interesting to realize that AD's and DNN don't mesh well in its current implementation. Oddly enough I have found myself with the the same struggles most folks experience with integrating AD and DNN.
I thought about creating my own, but to keep the DNN community spirit, I'd like to foster renewed thinking how AD could be implemented.
I have a couple of AD successes recently using 4.8x of DNN. 4.9.x, no so much. Which indicates to me that the core changes faster than the providers do. imho, the AD provider model may be to cumbersome to wire up to. Now that IIS7, pipelining, and Windows2008 server is in the mix, many providers may break anyway (even though a one-off AD provider's core is flawless)
I'm going to go off on a limb here and say, "Single Sign-on (SSO) is dead!" Now, hold on. :-) In the context of private intranet DNN site, SSO is not. But let's face it, logging onto a page and having the annoying login box is sooo very IIS3ish. I cerntainly know that login box is a pain for the AD provider.
So, let's say we forget Windows Auth completly for a moment... go ahead...take a brisk walk around the block to clear your mind. :-) This post will be around.
..ok, welcome back. :-)
Forget code for a moment and pretend your at home on your private computer and want to log into your corporate DNN site. Naturally, you're going to have to login in. So, let's assume you enter: MyID and MyPwd and click login. Do you really care how your authenticated? Nope, not in the least.
Stay tuned...