Book Image

ASP.NET Core MVC 2.0 Cookbook

By : Jason De Oliveira, Engin Polat, Stephane Belkheraz
Book Image

ASP.NET Core MVC 2.0 Cookbook

By: Jason De Oliveira, Engin Polat, Stephane Belkheraz

Overview of this book

The ASP.NET Core 2.0 Framework has been designed to meet all the needs of today’s web developers. It provides better control, support for test-driven development, and cleaner code. Moreover, it’s lightweight and allows you to run apps on Windows, OSX and Linux, making it the most popular web framework with modern day developers. This book takes a unique approach to web development, using real-world examples to guide you through problems with ASP.NET Core 2.0 web applications. It covers Visual Studio 2017- and ASP.NET Core 2.0-specifc changes and provides general MVC development recipes. It explores setting up .NET Core, Visual Studio 2017, Node.js modules, and NuGet. Next, it shows you how to work with Inversion of Control data pattern and caching. We explore everyday ASP.NET Core MVC 2.0 patterns and go beyond it into troubleshooting. Finally, we lead you through migrating, hosting, and deploying your code. By the end of the book, you’ll not only have explored every aspect of ASP.NET Core MVC 2.0, you’ll also have a reference you can keep coming back to whenever you need to get the job done.
Table of Contents (26 chapters)
Title Page
Copyright and Credits
Packt Upsell
Contributors
Preface
Index

Authentication using authorization servers


If someone tries to access a secure part of your web app and they haven't logged in yet, the app redirects the user to the authorization server to identify themself. Mostly, this means users enter their credentials (username, email, password, and so on.)

The Authorization server one job to do, authenticate the user with their credentials and return claims back.

Note

Claims are basically granted privileges lists. A user can have multiple claims to use portions of an app, such as viewing billing history, adding a bill, deleting a bill from history are different claims.

Once the authorization server validates the user with the provided credentials, it generates a token that is mapped to the user, and it either issues that token to the user or redirects the user to the app.

If a user tries to access a secure part of your web app, it'll check the token and authorize the user if the token is valid.

Some authorization servers: