Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
ASP.NET Core MVC 2.0 Cookbook

You're reading from   ASP.NET Core MVC 2.0 Cookbook Effective ways to build modern, interactive web applications with ASP.NET Core MVC 2.0

Arrow left icon
Product type Paperback
Published in Feb 2018
Publisher
ISBN-13 9781785886751
Length 668 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Authors (3):
Arrow left icon
Engin Polat Engin Polat
Author Profile Icon Engin Polat
Engin Polat
Jason De Oliveira Jason De Oliveira
Author Profile Icon Jason De Oliveira
Jason De Oliveira
Stephane Belkheraz Stephane Belkheraz
Author Profile Icon Stephane Belkheraz
Stephane Belkheraz
Arrow right icon
View More author details
Toc

Table of Contents (21) Chapters Close

Preface 1. Cross-Platform with .NET Core 2. Visual Studio 2017, C# 6, IDEs, and Roslyn FREE CHAPTER 3. Working with npm, Frontend Package Managers, and Task Runners 4. Reusing Code with NuGet 5. SOLID Principles, Inversion of Control, and Dependency Injection 6. Data Access - EF7 with Repository, SQL Server, and Stored Procedures 7. Accessing data with Micro ORMs, NoSQL, and Azure 8. Cache and Session - Distributed, Server, and Client 9. Routing 10. ASP.NET Core MVC 11. Web API 12. Filters 13. Views, Models, and ViewModels 14. Razor and Views 15. TagHelpers and ViewComponents 16. OWIN and Middleware 17. Security 18. Frontend Development 19. Deployment and Hosting 20. Other Books You May Enjoy

Introduction

In this section, we will take a look at how authentication works in ASP.NET Core.

All examples in this chapter can be found at https://github.com/polatengin/B05277/tree/master/Chapter17 GitHub repo.

The HTTP protocol is a stateless, response-for-a-request based protocol. This means an HTTP server can generate a response once it gets a request, and it never remembers previous requests and their results. Every request is processed separately.

For example, if an application requires you to log in first, a developer should handle the required logic flow to redirect to the user login page if they haven't logged in yet.

So, every request should have all the information to be processed successfully (if a user has logged in or not, who the user is, and their permissions.)

If a bad user sits on the line between the client and the server, they can read packages and...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at AU $24.99/month. Cancel anytime