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
Hands-On Design Patterns with C# and .NET Core

You're reading from   Hands-On Design Patterns with C# and .NET Core Write clean and maintainable code by using reusable solutions to common software design problems

Arrow left icon
Product type Paperback
Published in Jul 2019
Publisher Packt
ISBN-13 9781789133646
Length 410 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Authors (2):
Arrow left icon
Jeffrey Chilberto Jeffrey Chilberto
Author Profile Icon Jeffrey Chilberto
Jeffrey Chilberto
Gaurav Aroraa Gaurav Aroraa
Author Profile Icon Gaurav Aroraa
Gaurav Aroraa
Arrow right icon
View More author details
Toc

Table of Contents (19) Chapters Close

Preface 1. Section 1: Essentials of Design Patterns in C# and .NET Core FREE CHAPTER
2. Overview of OOP in .NET Core and C# 3. Modern Software Design Patterns and Principles 4. Section 2: Deep Dive into Utilities and Patterns in .NET Core
5. Implementing Design Patterns - Basics Part 1 6. Implementing Design Patterns - Basics Part 2 7. Implementing Design Patterns - .NET Core 8. Implementing Design Patterns for Web Applications - Part 1 9. Implementing Design Patterns for Web Applications - Part 2 10. Section 3: Functional Programming, Reactive Programming, and Coding for the Cloud
11. Concurrent Programming in .NET Core 12. Functional Programming Practices 13. Reactive Programming Patterns and Techniques 14. Advanced Database Design and Application Techniques 15. Coding for the Cloud 16. Miscellaneous Best Practices 17. Assessments 18. Other Books You May Enjoy

Authentication and authorization

In the previous chapter—where we started upgrading our console application to a web application—we added Create, Read, Update, and Delete (CRUD) operations, which are available publicly to any user who is able to perform them. There is nothing coded to restrict a particular user from performing these operations. The risk with this is that users who are not supposed to perform these operations can easily do so. The consequences of this are as follows:

  • Unattended access
  • An open door for hackers/attackers
  • Data leakage issues

Now, if we are keen to safeguard our application and restrict the operations to permitted users only, then we have to implement a design that only allows these users to perform operations. There may be scenarios in which we could allow open access for a few operations. In our case, most operations are only for...

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 $19.99/month. Cancel anytime