Implementing Security in ASP.NET Core: Claims, Patterns, and Policies

There are two sides to security: Authentication and Authorization. Authentication is logging in to an application and establishing who you are. Authorization is figuring out what the user can do and ensuring that they can’t do things that they aren’t supposed to.  I don’t know about you but sometimes it feels like everyone focuses on authentication and forgets about the authorization stuff.

 

In this session, we’ll focus on implementing Authorization in ASP.NET Core MVC and WebAPI. We’ll talk about claims-based security in ASP.NET Core, writing custom ASP.NET Core Middleware, authorizing using ASP.NET Policies, Authentication Requirements, and Authentication Handlers. Along the way, we’ll talk about how to use the Strategy Pattern to encapsulate authorization decisions in your app so that your security code stays clean and maintainable.

 

Benjamin Day is a consultant and trainer specializing in software best practices using Scrum with Microsoft’s DevOps tools. Ben’s main areas of emphasis include Team Foundation Server, Scrum, software testing, and software architecture. He is a Microsoft Visual Studio ALM MVP, a certified Scrum trainer via Scrum.org, and a speaker at conferences such as TechEd and Visual Studio Live! When not developing software, Ben’s been known to go running and sea kayaking in order to balance out his love of cheese, cured meats, and champagne. He can be contacted via http://www.benday.com.

 

Pizza, drinks and conversation will follow our speaker!

As usual, after we wrap our pizza break we will be holding another CINARC (Cincinnati Software Architecture Group). This session will feature more discussion on topics chosen the night of the meeting. The focus of the meeting will be to discuss issues of software architecture relevant to the members of the community.