I have an issue with usage of session state variables from within the umbraco client with following scenario:

1. A website user is hitting a ASPX on wich a session state variabele is set with some ID
2. The same user is succesfully logging in into umbraco (/umbraco/umbraco.aspx)
3. The afterNodeRender event uses the session variabele to remove certain nodes from the XmlTree (depending on the ID value in session variable)

But it seems that the session variabele is cleared at step 2. When debugging on the ASPX page (step 1) which is setting the session, and the event-handler that is called from the umbraco client (step 3) I found that a whole new session was created when logging into umbraco. Session.SessionID get an new value...

I am puzzled...

Has anyone an idea to prevent umbraco from creating a new session after logging in, or is there something I am missing here?

Nico