Custom implementation of IPrincipal throws System.SystemException: The trust relationship?

I thought that it was the WindowsAuthenticationModule that added WindowsPrincipal to HttpContext. User, but removing that still gave the same issue. That was implied in this article: msdn.microsoft.com/en-us/library/ff64707... I tried setting AppDomain.CurrentDomain.

SetPrincipalPolicy( PrincipalPolicy. NoPrincipal) on appstart and OnAuthenticateRequest as the suggested but to no avail However, this worked (in OnAuthenticateRequest): Context. User = new GenericPrincipal(new GenericIdentity(String.

Empty), new string0) I will settle for this for now. Thanks for everyones input!

I thought that it was the WindowsAuthenticationModule that added WindowsPrincipal to HttpContext. User, but removing that still gave the same issue. That was implied in this article: msdn.microsoft.com/en-us/library/ff64707... I tried setting AppDomain.CurrentDomain.

SetPrincipalPolicy( PrincipalPolicy. NoPrincipal); on appstart and OnAuthenticateRequest as the suggested but to no avail. However, this worked (in OnAuthenticateRequest): Context.

User = new GenericPrincipal(new GenericIdentity(String. Empty), new string0); I will settle for this for now. Thanks for everyones input!

Global. Asax OnAuthenticationRequest – onof Aug 3 '10 at 10:06.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.