I have written a custom login page that authenticates to Novell eDirectory.  This page resides in an ASP.Net 2.0 web application that is the parent directory to my DNN site.  I have implemented single sign on so that the cookie can be shared among multiple sites (this is an intranet application).  I have the web.config in the parent application check if the user is authenticated and the web.config in my DNN module redirect to the appropriate login page.  Because the web.config files do all of the work for checking if a user is authenticated, I enabled anonymous logins in DNN. In DNN v.04.06.02, after my custom login page authenticates the user, if that user is not registered on the DNN site, the login control displays no user name, but treats the anonymous user as logged in.  Users that are allowed edit permissions are registered on the DNN site, and the login control displays the appropriate user name for them, and allows them to perform edits.  That is all working very nicely.

The problem is that when I upgraded the site to DNN 4.7, and keep my web.config files ostensibly the same, the login control seems to recognize that the user does not exist in the database, and redirects back to the custom login page in a never ending loop, unless the user has been assigned edit permissions and therefore exists in the database.  When I change the web.config file in the parent directory to allow users="*", unauthenticated users are allowed access as expected.

What has changed in DNN 4.7?  I went back to 4.6 for the time being.  I really have no desire to recreate the entire contents of my Novell edirectory in DNN, less than 20 users will need to make edits to the site.