- Популярные видео
- Авто
- Видео-блоги
- ДТП, аварии
- Для маленьких
- Еда, напитки
- Животные
- Закон и право
- Знаменитости
- Игры
- Искусство
- Комедии
- Красота, мода
- Кулинария, рецепты
- Люди
- Мото
- Музыка
- Мультфильмы
- Наука, технологии
- Новости
- Образование
- Политика
- Праздники
- Приколы
- Природа
- Происшествия
- Путешествия
- Развлечения
- Ржач
- Семья
- Сериалы
- Спорт
- Стиль жизни
- ТВ передачи
- Танцы
- Технологии
- Товары
- Ужасы
- Фильмы
- Шоу-бизнес
- Юмор
ASP.NET Core Authentication with Custom Handler
In my last video, I have discussed how to use JWT for authentication in ASP.NET Core application.
In this video, we will be using our own token generator. And hence our own custom authentication handler.
A custom authentication handler in ASP.NET Core needs to derive from AuthenticationHandler, is is a generic class. Where T is derived from AuthenticationSchemeOptions.
In this video, for simplicity, I have using a GUID for a token. But in real-life solutions, we will use encrypted values using a private key. So that it is more secure. Also, the token will have time to live. Just like the JWT Token creation process supports time to live.
In the example for keeping a track of the tokens, I have created a in-memory dictionary. But in real-life solution, it would be some sort of distributed cache like Redis as the web servers will be distributed across multiple containers. So keeping an in-memory cache will not work.
Blog url: https://dotnetcorecentral.com/blog/authentication-handler-in-asp-net-core/
Видео ASP.NET Core Authentication with Custom Handler канала DotNet Core Central
In this video, we will be using our own token generator. And hence our own custom authentication handler.
A custom authentication handler in ASP.NET Core needs to derive from AuthenticationHandler, is is a generic class. Where T is derived from AuthenticationSchemeOptions.
In this video, for simplicity, I have using a GUID for a token. But in real-life solutions, we will use encrypted values using a private key. So that it is more secure. Also, the token will have time to live. Just like the JWT Token creation process supports time to live.
In the example for keeping a track of the tokens, I have created a in-memory dictionary. But in real-life solution, it would be some sort of distributed cache like Redis as the web servers will be distributed across multiple containers. So keeping an in-memory cache will not work.
Blog url: https://dotnetcorecentral.com/blog/authentication-handler-in-asp-net-core/
Видео ASP.NET Core Authentication with Custom Handler канала DotNet Core Central
Комментарии отсутствуют
Информация о видео
5 января 2020 г. 13:05:23
00:20:36
Другие видео канала


![An introduction to FusionCache [.NET 8]](https://i.ytimg.com/vi/-ijPI53-mdA/default.jpg)


![Extension Methods (An Introduction for .NET Developers [.NET 5 and C#])](https://i.ytimg.com/vi/v_cgQzp8YHQ/default.jpg)
![Memento Design Pattern (An Introduction for .NET Developers [.NET 6 and C# 10])](https://i.ytimg.com/vi/G82F85SqYUs/default.jpg)





![OpenTelemetry with Semantic Kernel AI Agent in ASP.NET Web API [C#/.NET]](https://i.ytimg.com/vi/kLfGLC__onA/default.jpg)
![How to pass test parameters to MSTest methods [C# 11/.NET 7]](https://i.ytimg.com/vi/XFn-rQ-C2Cg/default.jpg)







![Class, Constructor, Function, and Property in C# [C# Fundamental series, examples in .NET 6 ]](https://i.ytimg.com/vi/RpuuThqrKmY/default.jpg)