Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

How do you unit test web page authorization using ASP.NET MVC?

Let's say you have a profile page that can only be accessed by the owner of that profile. This profile page is located at:

User/Profile/{userID}

Now, I imagine in order to prevent access to this page by other users, you could structure your UserController class's Profile function to check the current session's identity:

HttpContext.Current.User.Identity.Name

If the id matches the one in the url, then you proceed. Otherwise you redirect to some sort of error page.

My question is how do you unit test something like this? I'm guessing that you need to use some sort of dependency injection instead of the HttpContext in the controller to do the check on, but I am unclear what the best way to do that is. Any advice would be helpful.

like image 437
Kevin Pang Avatar asked Sep 25 '08 06:09

Kevin Pang


2 Answers

The link above is a good one. I would also add that instead of programmatically checking the User.Identity.Name value, you should use the Authorize attributes as outlined in the article:

http://weblogs.asp.net/scottgu/archive/2008/07/14/asp-net-mvc-preview-4-release-part-1.aspx

like image 95
Brian Vallelunga Avatar answered Oct 10 '22 17:10

Brian Vallelunga


I ended up going with the "UserNameFilter" shown in Kazi Manzur's blog post. Works like a charm and easy to unit test.

like image 37
Kevin Pang Avatar answered Oct 10 '22 19:10

Kevin Pang