Announcing: Securing ASP.NET Core 2 with OAuth2 and OpenID Connect Course Published at Pluralsight

A while ago I created a Pluralsight course focused on securing ASP.NET Core with OAuth2 and OpenID Connect.  That one was built using ASP.NET Core 1.1.  I got a lot questions asking for a new course that would focus on ASP.NET Core 2, as quite a bit changed in regards to authentication/authorization between Core 1 & 2.  Today I’m happy to announce that that new course, Securing ASP.NET Core 2 with OAuth2 and OpenID Connect went live! 

Here’s what you can expect:

Knowing how to secure applications is important, but knowing why we make certain decisions is, arguably, even more important. In this course, Securing ASP.NET Core 2 with OAuth2 and OpenID Connect, you’ll learn the ins and outs of OAuth2 and OpenID Connect (OIDC), being today’s widely-used standards. First, you’ll explore what these standards entail, and how you can integrate their implementations in ASP.NET Core with IdentityServer4. Next, you’ll discover how to secure both a web app and an API. Finally, you’ll learn how to use authorization policies and deal with expired access. By the end of this course, you’ll have the necessary knowledge to efficiently secure your ASP.NET Core 2 applications.

You can watch the course at Pluralsight.  If you don’t have an account yet, don’t worry: you can easily start with a free trial.

Happy coding! :)

PS: for those of you wondering what’s next: I’m currently working on a course that’ll focus on building async APIs with ASP.NET Core, including some in-depth coverage of how async works in ASP.NET Core and what it can help with.  ETA: after the summer.

 Tweet about this on TwitterShare on LinkedInShare on Facebook

2 Comments

Seth

Thanks Kevin! This one was great! Quick question though, I am working on a simple API application that sends a message using a third party SMS service. The clients will be mobile applications and client-side web apps that will allow users to send an invite to use the app via this API. We can’t make the users log in to use the API, just need to verify that the client app is authorized. Any advice?

Reply

Leave a Reply

Your email address will not be published. Required fields are marked *