Yes, I just talked to Ray, and he is aware of the problem, we will need to look into using a different control to fix the issue. it will p[robably take a couple of weeks for a fix to be released for this one.
in the mean time, you can work around it by manually editing the code. in the login page, you will see code similar to this that sets the session variables:
"sessionColumns" => explode($WA_Auth_Separator,"UserID"),
"sessionNames" => explode($WA_Auth_Separator,"SecurityAssist_UserID"),
you can add another session variable by editing that code:
"sessionColumns" => explode($WA_Auth_Separator,"UserID",$WA_Auth_Separator,"ColumnName",$WA_Auth_Separator),
"sessionNames" => explode($WA_Auth_Separator,"SecurityAssist_UserID",$WA_Auth_Separator,"SessionName",$WA_Auth_Separator),