I implemented testing for the mmUserSecurity_RedirectionUrl and it works flawlessly in development. When I login and logout again, it is redirecting to the correct page. The problem still is when I deployed it this morning to the server I still get the message that I am logged in, but it doesn't redirect anywhere.

This is frustrating since it works fine in developer mode, and I am trying to push Mere Mortals as a standard platform. It looks as if I may have to choose another form of security, since MM's security seems kind of hokey in test server mode. It is obvious to me that it is Mere Mortals, because it looks as if it is a MessageDisplay.aspx page from Mere Mortals that is displaying. So I don't think it is our server environment's configuration

In my HookUserAuthenticated method I have the following code:

if (Session["mmUserSecurity_RedirectionUrl"] == null)
{
Session["mmUserSecurity_RedirectionUrl"] = "default.aspx";
}

So it should always go to the default.aspx page if there are any problems. In my default.aspx page load is the following:

//Retrieve Default WebConfig Settings
this.defaultHomePage = ConfigurationSettings.AppSettings["DefaultHomePage"];
this.defaultTimeout = Convert.ToInt32(ConfigurationSettings.AppSettings["DefaultTimeout"]);

if (Page.Request.QueryString["Mode"] != null)
{
string Mode = this.Page.Request.QueryString["Mode"].ToString().Trim();

if (Mode == "Logout")
{
mmBaseUserLogin.Logout();
Response.Redirect("UserLogin.aspx");
}
else if (Mode == "Refresh")
{
this.UpdateDemographics();

Response.Redirect(this.defaultHomePage);
}
}
else
{
Response.Redirect(this.defaultHomePage.Trim());
}