ASP.NET Core Dynamic Authorization (.NET 7 Minimal Apis C#)

preview_player
Показать описание


🕰 Timestamps
00:00 Introduction
02:22 Generating Permissions
03:28 Background Refreshing
11:04 Authorization Policy

👉 Try Rider
RD5K9-4TXXW-KMV3G-NYWSF-3ZSTP

#aspnetcore #authentication #authorization
Рекомендации по теме
Комментарии
Автор

If you are asking - how do I generate claims for controllers?

RawCoding
Автор

Insanely cool stuff. Tbh, I won't probably use it in my whole commerical programming life, but the video and the whole topic is very interesting

mykhailokonontsev
Автор

Thanks so much for the deep dive into ASP.NET Core security! 😎👍

TheJohndward
Автор

Thank you for sharing. Finally decided to become a patron too.

reagang
Автор

Thank you Anton, beautifully done, as always.
I would like to clear a thing in my mind. What is the difference *between* having an endpoint that hash a Tag/Identifier for accessing this endpoint (the way I understood it, is that is the permissionId what could also be a Guid.ToString()) *AND* an endpoint requiring a claim.
The user will need to have *either* the claim *or* the "permissionId" to access the endpoint. The endpoint will statically always have some "demand".

So, what is the "Dynamic" part here ? Is it that it is easier to Add/Remove permissions from DB instead of updating the claims from the User ? For example, the cookie cannot get updated, unless you re-sign-in.
So essentially, what is the difference of having a user that has a claim that an endpoint demands, *and* having an endpoint that has some permissionIds and give those permissions to the user.

MrJonnis
Автор

Thank you very much for this video! I have a question tags attribute changes the way methods are displayed in swagger, is there any way to prevent tags from affecting it?

JakubSzczypa-nw
Автор

I couldn't get the tip page to work. Have an LN public addr?

woodandgears
Автор

Yò stupid question here, but i guess those are the most important, how can i return a feedback to the client from this ? i saw you can add some fail reasons but i just get the html page as a result

i did it like this
if(user == null)
{
context.Fail(new AuthorizationFailureReason(this, "Your token expired!"));
return Task.CompletedTask;
}

camenraidercc
Автор

hi, thanks for this awesome lecture, please upload related code with each video, its request

abdulnaveed
Автор

Speaking too fast ... Please help us from outsite US. Rssss

marquesw