I guess I'll reply to this since I'm not seeing any action on it, hopefully it helps someone asking the same question.
Before I asked the above question I had done several hours of searching and digging but only found one older post that said something to the effect of "Dynamic Login is not compatible with Active Directory." That post was made prior to the release of your provider though which is why I continued with my question.
Apparently that's still the case, and the page that advertises the login provider is a little misleading. If I'm incorrect I'd LOVE a correction and information on how to make things work the way I really want.
The thing I really wanted this for was to use the DropDown Login skin object. So, since I couldn't get that to work with AD I did the following: 1. Added DropDown Login to my skin 2. Created a login page called Secure Login with the regular DNN Login on it 3. Disabled all login providers on my portal except Active Directory (this removes all the extra buttons from the DNN Login (Standard, Windows, etc) and it will only authenticate against Active Directory. 4. Added a Windows logo link to DesktopModules/DropDown-Login/LoginUser.ascx that had the link URL formatted as "/SecureLogin.aspx"
Whala, non-Intranet users use the DropDown Login and are authenticated against DotNetNuke, Intranet users have an extra step of clicking on the Windows logo inside DropDown Login (oh well). This means all portals where I want to implement DropDown Login will need a Secure Login page, but we had adopted that standard anyways.
|