How do I mock User.Identity.GetUserId()?

Question

I am trying to unit test my code which includes the line:

UserLoginInfo userIdentity = UserManager.GetLogins(User.Identity.GetUserId()).FirstOrDefault();

I'm just stuck on one bit as I can't get:

User.Identity.GetUserId()

to return a value. I have been trying the following in the set-up of my controller:

var mock = new Mock<ControllerContext>(); mock.Setup(p => p.HttpContext.User.Identity.GetUserId()).Returns("string");

But it gives an error of "NotSupportedException was unhandled by user code". I have also tried the following:

ControllerContext controllerContext = new ControllerContext(); string username = "username"; string userid = Guid.NewGuid().ToString("N"); //could be a constant List<Claim> claims = new List<Claim>{ new Claim("http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name", username), new Claim("http://schemas.xmlsoap.org/ws/2005/05/identity/claims/nameidentifier", userid) }; var genericIdentity = new GenericIdentity("Andrew"); genericIdentity.AddClaims(claims); var genericPrincipal = new GenericPrincipal(genericIdentity, new string[] { }); controllerContext.HttpContext.User = genericPrincipal;

Based on some code I found on stackoverflow, but this returns the same error "NotSupportedException was unhandled by user code".

Any help as to how I proceed would be appreciated. Thanks.

The standard way to achieve that is to create a new service, i.e. IIdentity that abstracts your code from the GetUserId extension method and set it as a dependency on the code that is calling your UserManager — Sebastian Piu
– Sebastian Piu, Commented Mar 31, 2014 at 13:51
Just realized my original answer only worked for derived ApiControllers. Updated my answer with an option for derived Controllers as well, plus a second approach that works for both. — joelmdev
– joelmdev, Commented Sep 11, 2014 at 18:36

andrewb · Accepted Answer · 2015-10-21 01:41:49Z

You can't mock extension methods directly, so your best bet is to drill down until you hit the properties and methods upon which the extension method depends that are mockable.

In this case, IIdentity.GetuUserId() is an extension method. I'd post it, but the library is not currently open source, so you'll have to see for yourself that GetUserId() depends on ClaimsIdentity.FindFirstValue(). As it turns out, that is also an extension method, but it depends on ClaimsIdentity.FindFirst(), which is marked virtual. Now we have our seam, so we can do the following:

var claim = new Claim("test", "IdOfYourChoosing"); var mockIdentity = Mock.Of<ClaimsIdentity>(ci => ci.FindFirst(It.IsAny<string>()) == claim); var controller = new MyController() { User = Mock.Of<IPrincipal>(ip => ip.Identity == mockIdentity) }; controller.User.Identity.GetUserId(); //returns "IdOfYourChoosing"

Update: I just realized that the solution I posted above only works for derived ApiControllers (as in, Web API). The MVC Controller class doesn't have a settable User property. Fortunately it's pretty easy to go in through the Controller's ControllerContext to achieve the desired effect:

var claim = new Claim("test", "IdOfYourChoosing"); var mockIdentity = Mock.Of<ClaimsIdentity>(ci => ci.FindFirst(It.IsAny<string>()) == claim); var mockContext = Mock.Of<ControllerContext>(cc => cc.HttpContext.User == mockIdentity); var controller = new MyController() { ControllerContext = mockContext };

However, if all you're going to be using the User object for is to get the user's Id, there's another approach that will work for either type of controller and requires a lot less code:

public class MyController: Controller //or ApiController { public Func<string> GetUserId; //For testing public MyController() { GetUserId = () => User.Identity.GetUserId(); } //controller actions }

Now instead of calling User.Identity.GetUserId() when you want the user's Id, you simply call GetUserId(). When you need to mock out the user Id in tests, you simply do it like this:

controller = new MyController() { GetUserId = () => "IdOfYourChoosing" };

There are pros and cons to both approaches. The first approach is more thorough and more flexible and uses seams that are already present on the two controller types, but it's also a lot more code and doesn't read nearly as well. The second approach is much cleaner and IMO more expressive, but it is extra code to maintain, and if you don't use the Func call to get the user's Id, your tests won't work. Choose whichever one works better for your situation.

+1 Configuring the call to ClaimsIdentity.FindFirst() solved my problem. Here is an example in FakeItEasy syntax for anyone using that: var fakeClaim = A.Fake<Claim>(x => x.WithArgumentsForConstructor(() => new Claim(ClaimTypes.NameIdentifier, FakeEmpIDString))); var fakeIdentity = A.Fake<ClaimsIdentity>(); A.CallTo(() => fakeIdentity.FindFirst(ClaimTypes.NameIdentifier)).Returns(fakeClaim); My setup looks a little different; can't set Controller.User property directly so I inject a ControllerContext & set its HttpContext.User property to a ClaimsPrinciple object.
Oof. The second worked flawlessly. Did this for grabbing the UserID and worked like a charm!
@joelmdev, what if the id is customized to be a long instead of string? How does your first approach work in that case?
@avidProgrammer I believe you'd just swap out var claim = new Claim("test", "IdOfYourChoosing"); with new Claim("test", "1234567", ClaimValueTypes.Integer64);. I haven't tested this, but if it doesn't work it should at least put you on the right path.

Joe Taylor · Accepted Answer · 2014-03-31 13:52:50Z

You can't set up the GetUserId method because it's an extension method. Instead you'll have to set up the name on the user's IIdentity property. GetUserId will use this to determine the UserId.

var context = new Mock<HttpContextBase>(); var mockIdentity = new Mock<IIdentity>(); context.SetupGet(x => x.User.Identity).Returns(mockIdentity.Object); mockIdentity.Setup(x => x.Name).Returns("test_name");

See this for more info: http://msdn.microsoft.com/en-us/library/microsoft.aspnet.identity.identityextensions.getuserid(v=vs.111).aspx

Turns out I was actually just doing something else stupid and this wasn't my issue at all. But your answer is correct. Thanks.

Haohmaru · Accepted Answer · 2016-10-06 14:40:21Z

This worked for me

using fakeiteasy

 var identity = new GenericIdentity("TestUsername"); identity.AddClaim(new Claim("http://schemas.xmlsoap.org/ws/2005/05/identity/claims/nameidentifier", "UserIdIWantReturned")); var fakePrincipal = A.Fake<IPrincipal>(); A.CallTo(() => fakePrincipal.Identity).Returns(identity); var _controller = new MyController { ControllerContext = A.Fake<ControllerContext>() }; A.CallTo(() => _controller.ControllerContext.HttpContext.User).Returns(fakePrincipal);

Now you can get values back from those IIdentity extention methods:

eg.

 var userid = _controller.User.Identity.GetUserId(); var userName = _controller.User.Identity.GetUserName();

When viewing the GetUserId() method with ILSpy it shows

public static string GetUserId(this IIdentity identity) { if (identity == null) { throw new ArgumentNullException("identity"); } ClaimsIdentity claimsIdentity = identity as ClaimsIdentity; if (claimsIdentity != null) { return claimsIdentity.FindFirstValue(http://schemas.xmlsoap.org/ws/2005/05/identity/claims/nameidentifier); } return null; }

So GetUserId needs the Claim "nameidentifier"

Collectives™ on Stack Overflow

How do I mock User.Identity.GetUserId()?

3 Answers 3

6 Comments

1 Comment

Comments

Linked

Hot Network Questions