I had to change the authentication line in <httpModules> to:
<add name="Authentication" type="DotNetNuke.Authentication.ActiveDirectory.HttpModules.AuthenticationModule, DotNetNuke.Authentication.ActiveDIrectory" />
Uncommenting the existing line threw an exception.
Otherwise the setup is the same as the last time.
I still have the same issues:
1. Configuring AD settings still results in failures for GC, Root Domain, and LDAP. This has been an issue since my first 4.? install and I simply ignore it and move on. I should note here that entering the wrong information for the domain name throws an exception so if you get a failed attempt to authenticate then you probably have the correct domain name (at least if you are in a single domain environment).
2. Information in the profile is still loaded in the wrong fields. They are correct in AD, just not in the DNN profile. If the code is finally available then I can fix it but finding users is going to be tough when the domain name is appended to the userid.
I'm not sure this was intended to introduce an update to the provider anyway so you might just wait for word in these forums for an update.