Just a heads up. Roles and advanced feature are intentionally left out of this video because I will do an advanced and best practices follow up video. Keep coding!
I have an interesting question, can we use auth0 just for authentication then if user is authenticated when they hit our api we add our own api custom claims to the token to handle authorization?
I think more topics about authentication and authorization in general would be great! Its necessary for nearly every project these days but there is so little good content online or and written by unknown people that you are not sure if you can trust!
There are plenty of videos out on this topic, yet your teaching style I find best. Please continue this topic also explaining how to refresh the tokens!
Instead of using an additional policy or attribute, i would suggest to add the custom claim "admin" as a "role" claim: var claims = new List() { new Claim(...), new Claim(...), new Claim("role", "admin"), new Claim("role", "..."), Then the controller/actions can be protected by using: [Authorize]
GOGO Nick! In postman, instead of adding header Authorization, having Bearer (space) token U may get the same results easier going to Authorization tab (1 left from Headers), choose Type Bearer Token and just past the token in the right panel
Great content as usual Nick! Keep it up and yes, please show us how you would do refresh token (I already implemented it but I find your implementations always cleaner and well thought of). Thanks! PS: maybe you can show how to add multiple Identity providers (facebook + google + custom) all at the same time.
I am doing this with okta but I use a combination of middleware and filter to programmatically add the policy to the Controller/Action. I was able to inject javascript to swagger and add the header programmatically to curl so that you don't have to use the swagger authorize UI manually.
can't believe I've been your subscriber all this time until I needed this video. By far the most concise explanation I've seen about jwt implementation.
An advanced feature that I've seen a million ways that would be awesome to see you discuss would be how we can do "Enterprise Isolation". What I mean with this is that say that we have a SaaS where an "Enterprise" can have a subscription and manage their own details. For the sake of simplicity the developers want to have one shared database for all customers, which makes setup easy but it's equally dangerous because were just one missing .Where(x => x.EnterpriseId == _userEnterpriseId) from exposing other customers data. How would you setup that sort of thing? For example query filters in EF are awesome, but they don't help when patching / adding items.
Thats the old way, now you better add the role as a claim to your policy, that way its mutch better to manage when your application grows or if some authorization stuff changes you just need to do it in one place
Thanks. You are a great teacher. If you speak a little in slower pace it will be easier for some people including me to grasp every piece of information. Just a suggestion...
Great video. What about api keys? Is there a clean way to have an endpoint require jwt auth, another having api-key auth requirement, and have both for the rest? An example of this would be great! I've done same like these in the past but never found a clean way to do it. I've tried looking into making an auth handler to implement permissions and having the api key be a permission but can't seem to get it the right way
02:23 - defaults 04:07 - jwt settings in appsettings 05:47 - add authorization. Put UseAuthentification after httpsRedirection and before MapContollers 06:20 - withoud tag Authorize - it will not work 08:42 - разграничение, для одних методов чекать авторизацию, а для других нет 10:10 - Policy 12:16 - custom attribute 14:32 - handle in minimal api 15:26 - swagger support
Glad to see you mix it up a bit by going back to some of the basic stuff nearly every application needs. I've used JWT authentication in a few apps, but I learned a few new tricks from this, thanks Nick!
Hey, thanks for this video. It was awesome. I have a question. I'm kinda knew using net core. I made a classic mvc app and I tried to protect my app putting an authorize decorator in all the controllers, but even when I'm logged in I can't access the controllers. I don't know if it's the way I'm invoking them. I have a menu with options and each option is an anchor html tag, where I use the tag helpers asp-controller and asp-action. Any thoughts?
Would be cool if you show in one of the next videos how to authenticate against Azure AD and lock down a Web-Application, so only users can use it when they are member of a specific group. :)
Hey Nick great video as always . I would love to see your approach for JWT tokens for implementing where a user can perform update and delete operations only for posts that are created by them.
Thanks for this wonderfull new video as always ;) I really would like you to show an implementation of refreshing JWT stored in any vault you want if it is possible :D
Hey Nick, Is there a specific reason why you use a custom claim and policy for your admin users instead of simple role based authorization? Or was this just done for the sake of showing off the custom policies?
I didn't get the names of where to store the keys instead of the configuration? (did you say aws secrets manager?) What would you use to store those keys for a local project?
i would have done by having the initial service implement the handler too and this way to can add this new pattern into the existing code until you need a real reason why it has to be it's own set of handler classes .. this way you can introduce this pattern into an existing code without having to through the code you already had.
JSON Phonetically JAsonWebToken - JAWT Some will then tell you it is actually JOT that just makes no sense at all I think it just confuses people and we should all just say J W T As to your question, I think we all want to see a video for Refreshing tokens. Thanks for the awesome videos Nick
I think it's time we stopped pushing JWT now we know better and have done for some time. That said, the functionality within netcore for authetication and authorization are quite nice.
Make a advanced video indetail on the refresh tokens and specially what will happen to the token then user logsout please I will be waiting for this video
Hello! Love the video, I am introducing myself with it, I have some doubts about the project of Identy.API Someone has the code source or can explain how implement it?
Thanks for the great video. I have one question. Why can't a hacker get the token from the network tab like any developer, but in the production environment? I know it is not possible and it would have been a disaster but why? Thanks again.
It's posible to have both identity validation for login UI and JWT authorization? I was trying this last weekend, and couldn't make them work at the same time. Love your content 🤙🏻
Associate a handler to the policy that checks the role in the claim with your determined list of allowed roles for the resource. You can also look up resource based auth.
@@jfpinero what if we also have roles tied to a resource. In example for application user has "User" role but in the resource it is Owner or Participant, where only Owner can perform Update, Delete actions ? Claims seem to be too much complicated to keep relationship between user roles and resources. For now i just make a call to a database to check if user X has role Owner in entity A
So authentication/authorization works on the api via an Identity provider. Fine, I'm okay with that. What I don't understand is how is my client application, say a razor pages app, supposed to work with this? I send a username and password to my API to login, the API returns the token and we're all great. What do I do with it then? I can embed it in an HttpOnly secure cookie, but that isn't enough to authorize the user to perform actions on the razor pages app, right? So how do I configure my app to use the token from the API to infer authorization status of a user?
@nickchapsas first of all thank you for sharing such good stuff always ... I am dying to see your video for refresh tokens have you made it if yes please give me link
Guys what would you recommend where i have role per resource (entity in table) which can be created by any user but then only Owner of entity can perform delete, update etc. For now I have just database call validating if user has Owner role in the resource, but wondering if there is better approach
Hi Nick, you always say the link to the code in the description below, but sorry, I have never seen a link to the code in the description in any video, Am I miss something?
Also wondering. For general application purpose per user I went for Claims with roles User, PremiumUser, Admin. But for resources which can have Owner, Viewer or Editor I'm doing database validation
This is an awesome video regarding claims and policies. The challenge though is to accept many claims under one policy; this works well when you have a user that falls under several claims. However, I think that the Authorization Attribute approach may be a better solution. With that said Nick, are those attributes "stackable" on a controller method?
Just a heads up. Roles and advanced feature are intentionally left out of this video because I will do an advanced and best practices follow up video. Keep coding!
Looking forward to that one!
You should do a RBAC vs ABAC video and their uses.
I have an interesting question, can we use auth0 just for authentication then if user is authenticated when they hit our api we add our own api custom claims to the token to handle authorization?
Looking forward to that one actually!
Please do explain and show roles implementation in detail
Can't wait! :D
I think more topics about authentication and authorization in general would be great! Its necessary for nearly every project these days but there is so little good content online or and written by unknown people that you are not sure if you can trust!
There are plenty of videos out on this topic, yet your teaching style I find best.
Please continue this topic also explaining how to refresh the tokens!
Instead of using an additional policy or attribute, i would suggest to add the custom claim "admin" as a "role" claim:
var claims = new List()
{
new Claim(...),
new Claim(...),
new Claim("role", "admin"),
new Claim("role", "..."),
Then the controller/actions can be protected by using:
[Authorize]
This should go in a handler that is associated to the policy instead of hardcoding directly in the controller
I always thought this is the best and most basic approach.
I think he did say that but just used admin like this for ease.
If it had been made 4 years ago, it would have saved me a lot of headaches. Now it was very refreshing and enjoyable.
A refresh token video would be coll. And also how to use JWT with asymmetric keys
GOGO Nick!
In postman, instead of adding header Authorization, having Bearer (space) token
U may get the same results easier going to Authorization tab (1 left from Headers), choose Type Bearer Token and just past the token in the right panel
What is the code of TokenGenerationRequest class?
Great content as usual Nick! Keep it up and yes, please show us how you would do refresh token (I already implemented it but I find your implementations always cleaner and well thought of). Thanks! PS: maybe you can show how to add multiple Identity providers (facebook + google + custom) all at the same time.
up
I am doing this with okta but I use a combination of middleware and filter to programmatically add the policy to the Controller/Action. I was able to inject javascript to swagger and add the header programmatically to curl so that you don't have to use the swagger authorize UI manually.
can't believe I've been your subscriber all this time until I needed this video. By far the most concise explanation I've seen about jwt implementation.
Source code would've been nice!
Thank you for this video. It was a great help for beginning with this topic. Would like to see some deep-dive videos into this topic.
An advanced feature that I've seen a million ways that would be awesome to see you discuss would be how we can do "Enterprise Isolation". What I mean with this is that say that we have a SaaS where an "Enterprise" can have a subscription and manage their own details. For the sake of simplicity the developers want to have one shared database for all customers, which makes setup easy but it's equally dangerous because were just one missing .Where(x => x.EnterpriseId == _userEnterpriseId) from exposing other customers data. How would you setup that sort of thing? For example query filters in EF are awesome, but they don't help when patching / adding items.
you could mention about Roles, for example Authorize(Roles = „admin”)
Thats the old way, now you better add the role as a claim to your policy, that way its mutch better to manage when your application grows or if some authorization stuff changes you just need to do it in one place
the refreshing part was always tricky for me, so Im interested in dedicated video A LOT :)
Hey Nick, thanks for this video and it would be far better if you make a video about the implementation of OAuth
you can actually set auth bearer token in authorization tab in postman. just saying
Thanks. You are a great teacher. If you speak a little in slower pace it will be easier for some people including me to grasp every piece of information. Just a suggestion...
If only you could give us OpenIdDict series. There is almost no content on this topic. I believe a lot of people will appreciate it :)
I was shocked at how sparse the OpenIdDict documentation was.
Great video. What about api keys? Is there a clean way to have an endpoint require jwt auth, another having api-key auth requirement, and have both for the rest? An example of this would be great! I've done same like these in the past but never found a clean way to do it. I've tried looking into making an auth handler to implement permissions and having the api key be a permission but can't seem to get it the right way
Did you find a solution for this use case?
Would be good to see how auth and Blazor WebAssemble play together :-)
I have the same interest, couldn't make it work
Finally full JWT tutorial. Thanks!
Great video!. Kindly show us how to refresh token as well. Thanks in advance
02:23 - defaults
04:07 - jwt settings in appsettings
05:47 - add authorization. Put UseAuthentification after httpsRedirection and before MapContollers
06:20 - withoud tag Authorize - it will not work
08:42 - разграничение, для одних методов чекать авторизацию, а для других нет
10:10 - Policy
12:16 - custom attribute
14:32 - handle in minimal api
15:26 - swagger support
Nice video! i'd love to see the video for the refresh token as well
I like to see a new video about authorization & authentication topics on .net 8
Thank you Nick, great video as always!
It would be great also to have a video about Refresh Tokens too. Thanks
Nice basic video. Would love to see refresh token video.
Thanks Nick, very useful and thorough explanation
Perfectly turned up just when I needed it.
Glad to see you mix it up a bit by going back to some of the basic stuff nearly every application needs. I've used JWT authentication in a few apps, but I learned a few new tricks from this, thanks Nick!
Great video - thanks Nick. Refresh token video please :)
Please add video to security refresh tokens
Great video and JWT Auth explanation. Thanks for the work
Hey, Can you make a video on Identity API
very helpful. would very much like to see more about this topics like refresh
Thank u for sharing this topic looking forward to more advanced options using this
Thanks for this video!
Was missing the correct issuer url in my case.
This came just at the right moment!
Great timing my dude! Want to implement JWT in my app atm.
we used IdentityServer now moving over to OpenIdicct... massive pain in the ...
Can you make a video about refresh tokens? It would be great ❤
I needed this video 4 days ago 😅 Do one for refreshing tokens aswell
Hey, thanks for this video. It was awesome. I have a question. I'm kinda knew using net core. I made a classic mvc app and I tried to protect my app putting an authorize decorator in all the controllers, but even when I'm logged in I can't access the controllers. I don't know if it's the way I'm invoking them. I have a menu with options and each option is an anchor html tag, where I use the tag helpers asp-controller and asp-action. Any thoughts?
Hi Nick very nice videp, please make a video about the refresh token. I am currently implementing this on a projet!
We want to see a video about refreshing tokens!
Would be cool if you show in one of the next videos how to authenticate against Azure AD and lock down a Web-Application, so only users can use it when they are member of a specific group. :)
Hello! Thanks for sharing this video! Would you also be willing to share the Github repo for this examples as well?
Hey Nick great video as always . I would love to see your approach for JWT tokens for implementing where a user can perform update and delete operations only for posts that are created by them.
Thanks for this wonderfull new video as always ;)
I really would like you to show an implementation of refreshing JWT stored in any vault you want if it is possible :D
Very nice video to teach the concepts🎉
Hey Nick,
Is there a specific reason why you use a custom claim and policy for your admin users instead of simple role based authorization? Or was this just done for the sake of showing off the custom policies?
It’s for the sake of showing off custom policies. I’m trying to have a basic barebones video so I can later do an advanced one that will show those
I didn't get the names of where to store the keys instead of the configuration? (did you say aws secrets manager?)
What would you use to store those keys for a local project?
i would have done by having the initial service implement the handler too and this way to can add this new pattern into the existing code until you need a real reason why it has to be it's own set of handler classes .. this way you can introduce this pattern into an existing code without having to through the code you already had.
Good video and it world be nice to have a video about refreshing
straight to the point. thanks!
JSON Phonetically JAsonWebToken - JAWT
Some will then tell you it is actually JOT that just makes no sense at all
I think it just confuses people and we should all just say J W T
As to your question, I think we all want to see a video for Refreshing tokens. Thanks for the awesome videos Nick
I'm confused...So its not a good practice to use the id_token when calling a API, it should be the acess token right?
I think it's time we stopped pushing JWT now we know better and have done for some time. That said, the functionality within netcore for authetication and authorization are quite nice.
What about asymmetric encryption. What is the best practice for api projects.
As what did you declare the CustomClaim in your TokenGenerationRequest ?
What is the difference between Claim and Signature? what does each one reference?
Make a advanced video indetail on the refresh tokens and specially what will happen to the token then user logsout please I will be waiting for this video
Is the sample source code available on GitHub?
This is super helpful. Thanks!
Hello! Love the video, I am introducing myself with it, I have some doubts about the project of Identy.API
Someone has the code source or can explain how implement it?
Can you make a video with Blazor WASM with Cognito Authentication thats uses groups to profiling the app content? Thank you!
@Nick could you do a video on a hybrid approach? Oidc like Okta/Auth0 for authentication (AUTHN) and local claims for Authorization (AUTHZ)
can we do refresh tokens too? i would like to know if some implementation i used is a good one
NIck a great video!! can you show the authorization using permission based please?
Is the Match method from OneOf library?
Minimal API with FastEndpoints FTW!!
Hey Nick, do you recommend using blazor for frontend?
When do you really create and manage this yourself compared to using oidc providers like IDS or Auth0?
Everyone Nick has worked with, ever
Why do you think it's acceptable to omit random words in speech?
Can you show how to "Refresh JWT Token" ?
Did you ever use OpenIddict ?
We need RefreshToken video ❤
Thanks for the great video. I have one question. Why can't a hacker get the token from the network tab like any developer, but in the production environment? I know it is not possible and it would have been a disaster but why? Thanks again.
Thanks for the video! Will you do some auth videos about Blazor WASM in the future? What about some resource-based authorization?
It's posible to have both identity validation for login UI and JWT authorization?
I was trying this last weekend, and couldn't make them work at the same time.
Love your content 🤙🏻
Great content. How to solve the case when the endpoint is accessed by the admin or the owner of the resource (move), e.g. downloaded from the DB?
Associate a handler to the policy that checks the role in the claim with your determined list of allowed roles for the resource. You can also look up resource based auth.
@@jfpinero what if we also have roles tied to a resource. In example for application user has "User" role but in the resource it is Owner or Participant, where only Owner can perform Update, Delete actions ? Claims seem to be too much complicated to keep relationship between user roles and resources. For now i just make a call to a database to check if user X has role Owner in entity A
Now waiting for Refreshing Token because without it this is only half implementation :)
So authentication/authorization works on the api via an Identity provider. Fine, I'm okay with that. What I don't understand is how is my client application, say a razor pages app, supposed to work with this? I send a username and password to my API to login, the API returns the token and we're all great. What do I do with it then? I can embed it in an HttpOnly secure cookie, but that isn't enough to authorize the user to perform actions on the razor pages app, right? So how do I configure my app to use the token from the API to infer authorization status of a user?
@nickchapsas first of all thank you for sharing such good stuff always ... I am dying to see your video for refresh tokens have you made it if yes please give me link
How to manage the token in JavaScript? How to make external complements use the token and be resistant to refresh. Thanks
Guys what would you recommend where i have role per resource (entity in table) which can be created by any user but then only Owner of entity can perform delete, update etc. For now I have just database call validating if user has Owner role in the resource, but wondering if there is better approach
Hi Nick, you always say the link to the code in the description below, but sorry, I have never seen a link to the code in the description in any video, Am I miss something?
It looks like a lot boiler plate code. There are not standard components for this?
Wait, we can use the James Webb Telescope to authenticate ourselves? 😅
No word on [Authorize(Roles = "Role1,Role2")] or User.IsInRole? ... which maps to the (default) role claim in the JWT
I already have oauth as my default authentication scheme for this one dotnet core app, can I tack jwt on to that?
idea - how many clims is too much claims and when we should store only id there and go for permission to database
Also wondering. For general application purpose per user I went for Claims with roles User, PremiumUser, Admin. But for resources which can have Owner, Viewer or Editor I'm doing database validation
Hey, Thanks for the great video, easy to follow, straight to the point. Would be nice if you could make one about refresh tokens.
Hey, how would we do that in a azure function? i'm struggling with that
Great video and very helpful. You just move really fast though. It's hard to see what you're doing.
Why would you HAVE to move to an identity provider if you could just issue your own tokens?
@nickchapsas Can we have source code used for this video ?
This is an awesome video regarding claims and policies. The challenge though is to accept many claims under one policy; this works well when you have a user that falls under several claims. However, I think that the Authorization Attribute approach may be a better solution. With that said Nick, are those attributes "stackable" on a controller method?