[Mono-bugs] [Bug 59683][Min] New - Setting Context.User does not update Thread.CurrentPrincipal

[bugzilla-daemon@bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by rainer.burgstaller@web.de.

http://bugzilla.ximian.com/show_bug.cgi?id=59683

--- shadow/59683	2004-06-07 03:30:14.000000000 -0400
+++ shadow/59683.tmp.7098	2004-06-07 03:30:14.000000000 -0400
@@ -0,0 +1,45 @@
+Bug#: 59683
+Product: Mono: Class Libraries
+Version: unspecified
+OS: Debian Woody
+OS Details: testing
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Minor
+Component: Sys.Web
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: rainer.burgstaller@web.de               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: Setting Context.User does not update Thread.CurrentPrincipal
+
+Description of Problem:
+When overriding the current principal (Context.User) in 
+Application_AuthenticateRequest, Thread.CurrentPrincipal does not get 
+updated. This is a difference to Microsofts implementation since there it 
+seems to be done. Since in many docs its mentioned to update Context.User 
+many examples wont work with mono.
+
+Steps to reproduce the problem:
+
+See attached source
+
+Actual Results:
+
+PrincipalPermission.Demand throws an exception.
+
+Expected Results:
+
+PrincipalPermission.Demand should pass.
+
+How often does this happen? 
+
+always
+
+
+Additional Information:
+
+Tested with mono beta1. Did not have time to test with beta 2 yet.