How to reset Thread.CurrentPrincipal for an unauthenticated unit test

Question

I have a library code that can be called from several types of clients, such as WinForms, Console, ASP.NET, etc ... and which should determine the current principal. In doing so, I perform a two-step verification of Thread.CurrentPrincipal and then Environment.UserName as follows:

var currentUser = !System.Threading.Thread.CurrentPrincipal.Identity.IsAuthenticated ? null : System.Threading.Thread.CurrentPrincipal.Identity.Name; if (string.IsNullOrWhiteSpace(currentUser)) { currentUser = Environment.UserName; } 

In the console application Thread.CurrentPrincipal.Identity.IsAuthenticated is always a false howerver in MSTest, it always has a valid authenticated user.

Is there a Thread.CurrentPrincipal value in the unit test for reset for unauthorized to simulate a console application?

Answer 1

All you have to do is:

 Thread.CurrentPrincipal = new GenericPrincipal(new GenericIdentity(""), new string[0]); 

Answer 2

I would rather create a class that implements all of the CurrentPrincipal with its proper interface and gets that interface when you need it.

You can then make fun of it in unit tests, making them simpler.