Cookie Authentication in ASP.NET 5

Posted by Anuraj on Thursday, February 5, 2015

.Net ASP.Net ASP.Net MVC

This post is about cookie based authentication in ASP.NET 5. I am implementing a cookie authentication in ASP.NET MVC application. Similar to other middleware components in ASP.NET, Cookie Authentication is also a middleware component, which you need to plug into ASP.NET pipeline.

For implementing cookie authentication, you require reference of Cookie middleware, here is the project.json file.

{
    "dependencies": {
        "Microsoft.AspNet.Diagnostics": "1.0.0-beta1",
        "Microsoft.AspNet.Hosting": "1.0.0-beta1",
        "Microsoft.AspNet.Mvc": "6.0.0-beta1",
        "Microsoft.AspNet.Server.WebListener": "1.0.0-beta1",
		"Microsoft.AspNet.Security": "1.0.0-beta1",
        "Microsoft.AspNet.Security.Cookies": "1.0.0-beta1",
		"Microsoft.AspNet.StaticFiles": "1.0.0-beta1",
	},
    "commands": {
        "web": "Microsoft.AspNet.Hosting --server Microsoft.AspNet.Server.WebListener --server.urls http://localhost:5001"
    },
	 "frameworks": {
        "aspnet50": {}
  }
}

All the components used in this project are available in ASP.NET Core Framework as well.

Now you need to plug the Cookie authentication module to use in ASP.NET pipeline, you can do this via Startup.cs file.

public class Startup
{
	public void Configure(IApplicationBuilder app)
	{
		app.UseErrorPage();

		app.UseServices(services =>
		{
			services.AddMvc();
		});
	
		app.UseCookieAuthentication(options => { 
			options.LoginPath = new PathString("/Home/Login"); 
		});
		app.UseMvc();						
	}       
}

Now, you need to apply the Authorize filter to protect resources, I am applying it in the class level. When there is a unauthorized request to such resource, filter returns 401 and the cookie middleware redirects to /Home/Login.

Note: You need to set the LoginPath property explicitly, otherwise it may not redirect.

[Authorize]
public class HomeController : Controller
{
	public IActionResult Index()
	{
		return View();
	}
}

And here is the Login action method, this code is for illustration purpose only, I not validating against database, if username and password matches the hard coded credentials, identity is established with that username.

[AllowAnonymous]
public IActionResult Login()
{
	return View();
}

[HttpPost, AllowAnonymous]
public IActionResult Login(User user)
{
	if(user.UserName == "admin" && user.Password == "Password")
	{
		var claims = new[]
		{
			new Claim("name", user.UserName)
		};
		var identity = new ClaimsIdentity(claims, 
			CookieAuthenticationDefaults.AuthenticationType);
		Context.Response.SignIn(identity);

		return Redirect("~/");
	}
	else
	{
		ModelState.AddModelError("LogOnError", 
			"The user name or password provided is incorrect.");
	}
	return View(user);
}

public IActionResult Logout()
{
	Context.Response.SignOut
	(CookieAuthenticationDefaults.AuthenticationType);
	return View("Login");
}

And here is the Login view

@using(Html.BeginForm())
{
	@Html.LabelFor(model => model.UserName)
	@Html.EditorFor(model => model.UserName)
	@Html.LabelFor(model => model.Password)
	@Html.PasswordFor(model => model.Password)
	<input type="submit" value="Sign In" />
	<br/>
	@Html.ValidationMessage("LogOnError")
}

To verify the implementation, install the required packages using kpm restore command, once it finishes, execute k web command. If web server is started, browse http://localhost:5001/, which will redirect to /Home/Login page, where you can enter the credentials, you will redirect back to /Home/Index page.

Happy Programming :)



Did you like this article? Share it with your friends

Facebook Twitter Google+ LinkedIn Reddit StumbleUpon



MVP
Subscribe


Copyright © 2017 - Anuraj P. Blog content licensed under the Creative Commons CC BY 2.5 | Unless otherwise stated or granted, code samples licensed under the MIT license. This is a personal blog. The opinions expressed here represent my own and not those of my employer. Hosted with ❤ by GitHub