Hi Nelsen

Are you sure you're logging your users out properly?

What does the code for logging users out look like?

/Jan

Hi I am using FormsAuthentication.SignOut()

The thing is if using ASP.Net membership provider http://our.umbraco.org/wiki/how-tos/membership-providers

Everything works OK but once you start working with umbraco Member that's where the problem is

Right now i just try to avoid calling Member.GetCurrentMember() cause even if i do FormsAuthentication.SignOut(), it still returns the old member

Let me show you my visual studio watch windows to show you what's happening 
http://files.nelsenlim.com/umbracoMembership47.png

Could it be it's because of the change in
http://umbraco.codeplex.com/workitem/30072

Thank u very much for your help

using .Net Reflector

public static bool IsLoggedOn()
{
    if (HttpContext.Current.User == null)
    {
        return false;
    }
    if (!HttpContext.Current.User.Identity.IsAuthenticated)
    {
        int id = CurrentMemberId();
        if (id > 0)
        {
            FormsAuthentication.SetAuthCookie(new Member(id).LoginName, true);
            return true;
        }
    }
    return HttpContext.Current.User.Identity.IsAuthenticated;
}

the call to isLoggedOn would cause a call us SetAuthCookie, i also found out that a cookie named "UMB_Member" is created when i am calling IsLoggedOn() .
The cookie name seems to be obtained from a constact in this class StateHelper.Cookies.Member

Right now to ensure everything is removed i do a

            int memberID = Member.CurrentMemberId();
            Member.ClearMemberFromClient(memberID);
           
            FormsAuthentication.SignOut();
            Session.Abandon();

Apparently just FormsAuthentication.SignOut(); is not enough

is working on a reply...