I found the problem (and will also post it to the question your asked in the community exchange).

Somewhere, and I didn't catch it in the late 6.2 betas/RC releases, but the core introduced their own FormsAuthentication httpModule. I've just discovered this but wanted to get an answer out ASAP and I haven't talked to any of the core engineers yet. What I think their FormAuthentication is for is the additional authentication types available (Facebook, Google, Twitter, New LiveID, Standard Login).

However, the AD provider also has a FormsAuthentication type that is needed for sites to run under the Integrated Pipeline that was written by, at the time, the IIS 7.0 project manager.

So, what's happening is on upgrade the AD provider's FormsAuthentication is getting overwritten by the Core's FormsAuthentication which is why you're just getting redirected to the login page.

The fix? Until I can either try to decompile the FormsAuthentication .dll given to me or I can talk to someone in the core code team and find a work around, at this time the only fix is to change the pipeline mode on your site to Classic (either Classic .NET AppPool or ASP.NET v4.0 Classic). I did try just re-installing the provider and that worked for AD logins but I couldn't logon any longer with standard DNN accounts.

My apologies to everyone for this. When the new providers were demo'd at a team meeting I asked if they'd break the AD module and was told they shouldn't. In my testing of the betas and RCs I was crunched for time and I only tested fresh installs and not upgrades so I missed this breaking change. I take full responsibility for this screw up and will try to come out with a fix as soon as I can.

Tanks for your feedback Mike, hope it will be easy to solve.
Wayne, if you can use autoconnect with success in classic mode I would know how do you do (can achieve it on my side).

---

Jean-Baptiste Bouillet Developer - Aricie

Hi Mike,

in fact in the system.web there is the system.web.security.formsauthenticationModule (so for IIS6) but in the system.webserver there already is the <add name="FormsAuthentication" type="Mvolo.Modules.FormsAuthModule" />.

Mvolo module is from dnn core or from dnn ad provider?

Even after cleaning the system.web section, autologin doesn't work anymore on my side. As explained in the tutorial, I select Anonymous+basic authentication for the website and for windowssignin.aspx I select Form+Windows Authentication.

I also tried to disable Anonmous at the side level and I get 401 error. If I apply windows authentication on all site I'm logged in but cannot logout to use dnn users.

---

Jean-Baptiste Bouillet Developer - Aricie