I have an issue where the SSL pages on my site do not see the user as being logged in between secure and standard pages. I was using 4.8 and just upgraded to 4.9. The issue still exists.
I have two URLs for my site, for example, www.mysite.org and secure.mysite.com, and both are the same instance of DNN on the same server. (Yes, at the moment one is a .org and the other a .com.) The user starts out at http://www.mysite.org and all works well. They log in normally to see their personalized info. When they attempt to view a secure page, DNN is supposed to automatically route them to http://secure.mysite.com, which is happening (and seems to be more reliable in 4.9.0, as 4.8.x would often not route to the secure URL if the user had not been there previously). When the user is redirected to a secure page which can only be viewed by registered users, DNN asks them to log in again. Why is this?
The next part of this issue is about a secure page that is visible to users of any type. The user visits the site via the standard URL (http://www.mysite.org), logs in successfully, and then chooses to view a page which is secure but visible to all users. In such a case, the screen makes it appear that the user has logged out (Login link appears on page), yet if the user clicks on another standard page, they once again appear logged in (name appears instead of Login link). Furthermore, when the user is on that secure page which makes them appear logged out, and they click on the Login link, nothing happens -- the link does not respond. How can I keep users logged in on such secure all-access pages?
Eric