Recently installed a new version of DNN 5.4.4 Everything seems great. However, we needed to lock the site down and require a login to see anything, including the home page. If I try to login to the site, I don't get an error, but neither the host nor a user which was created for testing can log in properly. Just keep getting dumped back on the Login page. Scenario - site A is dnn 5.2.2 and is called mystuff.myplace.com, site 2 is a DNN 5.4.4 site and is called morestuff.myplace.com Could logging into one be destroying the ability to login to the other? This only appears to happen in IE, from what I have seen. Also, we were changing the name of the home tab from home to "My Stuff Home". Any ideas?

Do you have a custom login page defined?

No, there is no custom login page defined. We can get to the login just fine - it simply doesn't work. You do not get an error, you simply get dumped back to the login page without being logged in. We have also reset the name of the homepage to "home", just to be sure that is not the issue. Still no luck.

Are you using a custom skin?  Sometimes, skins interfere with the javascript that controls the login/logout links.

Yes, we have a custom skin built in-house, but we removed the skin for testing since it had some javascript in it (an ie6 pngfix script).

Once I cleared cookies, we had less issues with logging in, but then we also started getting applicaiton errors. I changed the web.config to make them visible (customerrors set to "Off") and we were getting an encryption error.

I took a peek at the cookies and there were quite a few having to do with the root site (ex. "mystuff.com" and ".mystuff.com") - authentication etc. was inculded in some of those cookies.

We are creating a custom geolocator app that changes group permissions based on the users location, thus changing content, and also works for anonymous users. I beleive the issue stemmed from the custom app signing in the anonymous users. Then when you go to a subsite, which requires you to sign in, the cookie would interfere with signing in properly. Add to that there are two subsites users could sign in to (ex. "mystuff.myplace.com" and "morestuff.myplace.com") and it gets even more muddy.

We have changed the domains to new root domains (ex. "myplacestuff.com" and "myplacemorestuff.com") and that seems to be solving the issue as far as we have tested. It is difficult to tell at the moment, as it seems to be an intermittent and unpredictable problem. If anyone has seen this before, or knows of a solution, please post it here!


^_^