What's up all,
  I have a custom registration/profile module for my portals. In 4.4.1 (my previous version) it worked great, created users and updated user accounts just fine.

I have recently upgrade my dev system to 4.5.1 and now just the create user works.  Upon update of a users account and then redirection it logs the user out.

I have narrowed it down to the "Request.IsAuthenticated" is being set to false.  This is a read only property to I am not setting this.  It is set upon the "SetAuthCookie" in the login code.  Now obvioulsly I am not calling to log in the user after the update user is called.

Does this cookie get reset or something upon update user?  When is it "checked" and what does it check against?  Does the "HttpContext.Current.User.Identity" have anything to do with it?

Is there something I am missing with the 4.5.1 update user code? 

Thanks very much!