Basics Part 2b: The 'external authentication callback' Pattern

This is an excerpt from our 3-day training course called "Identity & Access Control for modern Applications using ASP.NET Core".

In this video we cover a common pattern that helps with onboarding users from external authentication systems to your ASP.NET Core application.

Basics Part 1: Introduction to ASP.NET Core Authentication & Authorization

Basics Part 2a: Adding external Authentication to your ASP.NET Core Application

Basics Part 2b: The "external authentication callback" Pattern

Basics Part 3: Using OpenID Connect for Authentication

[naunihalsidhu]

Firstly, Excellent Article, starting from basics and very clearly presented.
Can you create a Article on using this with Blazor Web Assembly ?

[fieryscorpion]

This was amazing! Can you create more videos like BFF, JWTs, API auth using OIDC, API keys and so on?

[mohammedazhar]

what is problem using the cookie "cookie" instead of "temp"?

[JamesterGo]

Does duende have a support where we can direct our concerns and questions?

[MistyKu]

Great explanation! There is one thing which I'm missing. How do you know that claim with e.g 'name' exists in a temp cookie? If it comes from external provider, there can be different claims depending on the external provider. There should some kind of mapping which maps external provider claims e.g from google to application claims.,

[sebastianolaf]

Great Video !!!
FYI, if anyone has problem with the callback. Looking at the directory structure between Google.cshtml vs Callback.cs.
The callback in "Google.cshtml.cs" is NOT Url.Page("Callback"); but must be with double dot like so Url.Page("../Callback");
Idk how in the video still can work.