One Week Only, Free Course at Pluralsight: OAuth2 and OIDC Strategies for Angular and ASP.NET

Some of you may already know this: each week, Pluralsight offers one of their courses for free, so you don’t need a subscription to access it.

I’m very happy to announce that this week, my course on OAuth2/OIDC, OAuth2 and OpenID Connect Strategies for Angular and ASP.NET, is that free course of the week.

A typical application these days consists of (at least) a client application and an API. In this practical, demo-driven course, you’ll learn how to work with authorization and authentication using today’s widely-used standards: OAuth2 and OpenID Connect. The focus of this course is security, both for Angular and ASP.NET MVC-based applications, but it aims to go beyond that. Amongst other things, we’ll look into finding a safe way to get identity-related information in your application over impersonation when accessing an API, right up to dealing with credentials and two-factor authentication.

So if you don’t have a Pluralsight account, but still want to learn a thing or two on that subject, now’s the time! :-)┬áHead over to the free weekly course page┬áto get started.

Happy coding! :)

 Tweet about this on TwitterShare on LinkedInShare on Facebook

One Comment

Greg Larson

Hello Kevin.
Thank you for the fantastic course “OAuth2 and OpenID Connect Strategies for Angular and ASP.NET”.
I have a question on the Single Sign-on section. You describe redirection from App A to IdentityServer to enter credentials, sign in and get the id_token as done earlier in the course.
Then, requesting a page from App B redirects to IdentityServer. IdentityServer see that we are already signed in and an id_token is returned to App B.
Question: How does IdentityServer know that App B is associated with the same user as App A?
I am missing the connections here.

Thank you,
Greg

Reply

Leave a Reply

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