Hi Mike,
first of all, thank you for distributing the beta.
I had a partial success installing the new beta: it appear to behave somewhat different on two different servers, but which are configured exactly the same way, and gives some errors in my customer AD forest.
I have a forest of 5/6 domains: DNN is configured with Active Directory authentication pointing to the local domain, and all domains are verified as accessible in AD authentication configuration page. The problem is that with previous version, 1,0, I could login with accounts from all of the domains in the forest, while now, wtih 1.0.3, only local accounts (of the local AD Domain) can login. Users from other domains are refused, and I find evetlog errors such as:
System.NullReferenceException: Object reference not set to an instance of an object. at DotNetNuke.Authentication.ActiveDirectory.ADSI.ADSIProvider.GetUser(String LoggedOnUserName, String LoggedOnPassword)
I'm collecting more info about this. The strange is I did not change configuration (which is the same as for ad provider for 1.0). More strange is I've got strange results, different results on 2 servers.
I've got a dev server, and a production one. Both win2003 with SQL Express, both on the same domain, same forest. Also, the dev server was aligned to the production one before starting these tests (DNN installation is identical, except for hostname and db connectionstring; db is identical). DNN 4.8.1 for both.
On the dev server, I had to add impersonation domain\user and password to web.config: without these, no way to get it running (exceptions avoid DNN to start). With impersonation configured, it starts but only authenticates users from the local domain.
On the production server, adding such info to web.config apparently does not produce any changes. I mean it works the same with or without this change: possible? What could be the reason for this? Anyway, It still does allow login only from the local domain.
When is next beta expected for? ;-)
thank you,
al.