Book Image

ASP.NET Core 5 for Beginners

By : Andreas Helland, Vincent Maverick Durano, Jeffrey Chilberto, Ed Price
Book Image

ASP.NET Core 5 for Beginners

By: Andreas Helland, Vincent Maverick Durano, Jeffrey Chilberto, Ed Price

Overview of this book

ASP.NET Core 5 for Beginners is a comprehensive introduction for those who are new to the framework. This condensed guide takes a practical and engaging approach to cover everything that you need to know to start using ASP.NET Core for building cloud-ready, modern web applications. The book starts with a brief introduction to the ASP.NET Core framework and highlights the new features in its latest release, ASP.NET Core 5. It then covers the improvements in cross-platform support, the view engines that will help you to understand web development, and the new frontend technologies available with Blazor for building interactive web UIs. As you advance, you’ll learn the fundamentals of the different frameworks and capabilities that ship with ASP.NET Core. You'll also get to grips with securing web apps with identity implementation, unit testing, and the latest in containers and cloud-native to deploy them to AWS and Microsoft Azure. Throughout the book, you’ll find clear and concise code samples that illustrate each concept along with the strategies and techniques that will help to develop scalable and robust web apps. By the end of this book, you’ll have learned how to leverage ASP.NET Core 5 to build and deploy dynamic websites and services in a variety of real-world scenarios.
Table of Contents (19 chapters)
Section 1 – Crawling
Section 2 – Walking
Section 3 – Running

Working with federated identity

Since you integrated with a specific AAD tenant assigned to you, it's easy to perceive it as your identity provider. Microsoft operates on a larger scale though, and on a technical level, you are federating with an external identity provider.

So, what does this actually mean?

Going back to our initial example from the real world, you could say that a passport is an example of federated identity. Even if you are not the entity issuing passports, you trust that there is a good procedure in place by the issuing authority and you accept it as proof of identity. You could choose to not trust this identity and build your own system for verifying that people are who they say they are, but it would most likely be time-consuming and expensive if you even managed to provide the same level of authenticity. How much of a hassle it is to order a passport in different countries probably varies, but just imagine how unfriendly it would be as a traveler...