I think the events you mentioned above are designed for a different purpose. Those are for when a user requests a page (perhaps through a bookmark) that requires login. In that case the page they requested is captured by the first event you listed and after login, the second event returns to that page with the user authenticated. You could capture a similar event on logout, but like you said, the session is invaldiated so most likely that will be wiped out. Only other thing I could think of is stuffing the page you want them to go back to in a cookie or something like that.