This is the amazing explanation regarding Api authentication and authorisation process along with real action demonstration. I really appreciate your efforts to make this concept easy to understand and digest. ❤️
This was very well done and great content. I would like to call out that, it is best practice to use a Reference Token for communicating from the UI to an API, in place of a jwt token. Jwt tokens are still a valid choice to use between services.
Hi, I Have a question. If we do not want to call RequireAuthorization on a endpoint (I just want the user to be authenticated for a specific endpoint and no other things needed like role etc.), it's not even validating the token. I mean, if token is not there it still returns result. What is happening here, could you please explain.
Claims are the pieces of information being asserted about a subject (the user, typically). The signature is used to verify that the sender of the JWT is who it says it is and to ensure that the message wasn't changed along the way.
Geraldson, generating tokens for real users involves introducing an identity provider, either built by yourself or already built for you. I cover that in my .NET microservices program, here: dotnetmicroservices.com/building-microservices-with-dotnet
![Lethal Company Music Video 🎵 "Follow The Orders" [VERSION A]](http://i.ytimg.com/vi/QeooZB4Z7RA/mqdefault.jpg)
This is the amazing explanation regarding Api authentication and authorisation process along with real action demonstration.
I really appreciate your efforts to make this concept easy to understand and digest. ❤️
Glad it was helpful, Vinay!
Finally a video where I understood the concept! Thanks
Glad it helped!
Great tutorial, I appreciate simplicity and you deliver quality content without any cumbersome code
Glad you like it!
Great tutorial, learned a new way to test the API without switching to postman, swagger or using curl. 🙂
Great to hear!
Thanks again! great as always!
Glad you liked it!
This was very well done and great content. I would like to call out that, it is best practice to use a Reference Token for communicating from the UI to an API, in place of a jwt token. Jwt tokens are still a valid choice to use between services.
Great tip Eldon!
Thing of beauty, thanks for the video
Glad you enjoyed it
@@juliocasal maybe something about modular architecture in the future? 👀
@@RaWMajkeL Modular architecture?
@@juliocasal I meant modular monolith pattern
You are simply Awesome Julio! Thank you for your efforts....
My pleasure!
Thanks, very much helpful 👌
Glad it helped!
Love ur explanation Julio, thanks for sharing
My pleasure!
Thank you
Hi, I Have a question. If we do not want to call RequireAuthorization on a endpoint (I just want the user to be authenticated for a specific endpoint and no other things needed like role etc.), it's not even validating the token. I mean, if token is not there it still returns result. What is happening here, could you please explain.
Without the RequireAuthorization call you basically have an anonymous endpoint. Call RequireAuthorization with no parameters instead.
What is the difference between Claim and Signature? what does each one reference?
Claims are the pieces of information being asserted about a subject (the user, typically). The signature is used to verify that the sender of the JWT is who it says it is and to ensure that the message wasn't changed along the way.
Thank you for this great tutorial
How I can generate a code and make register page and login
dotnet new blazor -au Individual
@@juliocasal I wanna make a webapi and for front-end I wanna use reactjs
how I can make this mix
Great content
Glad you think so!
How would I generate token for the users of my API with this package?
Geraldson, generating tokens for real users involves introducing an identity provider, either built by yourself or already built for you. I cover that in my .NET microservices program, here: dotnetmicroservices.com/building-microservices-with-dotnet
Bro should apply this into your Microservice course 🥲🥲
New .NET Bootcamp coming soon!