Identity and Access Control for Modern Applications
The ultimate guide to ASP.NET Core Authentication & Authorization, IdentityServer, OAuth 2, and OpenID Connect
Modern application design has changed quite a bit in recent years. “Mobile-first” and “cloud-ready” are the types of applications you are expected to develop. Also, to keep pace with these demands, Microsoft has revamped their complete web stack with ASP.NET Core to meet these architectural demands.
Needless to say, you also have to secure these apps.
Multi-platform, multi-client, and highly-mobile users bring a new set of challenges, so the approaches of the past are no longer appropriate for modern applications. This three-day workshop is your chance to dive into all things security related to these new technologies. Learn how to securely connect native and browser-based applications to your back-ends and integrate them with enterprise identity management systems as well as social identity providers and services.
This workshop covers everything you need to know to build modern and secure web, native & mobile applications. The foundation will be Microsoft’s latest technology stack, but will also include IdentityServer4, which is the officially recommended framework for building token services.
This workshop can be delivered onsite (contact us for more info), and publicly as listed below.
The full three day version of the class covers the following content and six hands-on labs.
You can also customize the content for one or two day versions.
The hands-on labs each take one to two hours and include step-by-step instructions and reference solutions.
In this lab you will add cookie-based authentication to the movie review website using the cookie authentication middleware and claims-based identity. Once users are authenticated, you will then also implement policy-based and resource-based authorization using the ASP.NET Core authorization framework.
In this lab you will remove the local authentication in the movie review application and change it to use external authentication. For the first part, you will use the OIDC protocol and use IdentityServer as the provider. For the second part, you will use social media accounts as the provider.
In this lab you will consolidate all external authentication into a single authentication gateway. IdentityServer will act as this gateway. You will also implement single sign-out which allows the user to sign-out of both the movie web app, and IdentityServer.
In this lab the movie review logic has been split into two projects: one for the back-end movie review logic as a web API, and one for the front-end movie review UI as a web application. The web API will require access tokens to use its functionality, and the movie review web app will obtain access tokens and pass them to the web API. IdentityServer will be used to issue this access token to the movie review web application.
n this lab the client application is a native, cross-platform console application. The pertinent steps in this lab will be the same if you're building a Windows or macOS desktop application, and are no different than if you were to use a platform-specific UI framework to build your application (WinForms, WPF, MacApp, Cocoa, GTK#, etc).