Asp.Net Core Web API Security Checklist. TOP 3 Vulnerabilities And How To Fix Them

[@oxioxy]

Clear and to the point, thank you!

[@Codewrinkles]

I'm happy you found it useful. Thanks for watching

[@Codewrinkles]

Glad it was helpful!

[@Tolmachovtv]

Thank you for such short and clear explanation, especially for practical examples

[@uzayrsyed6293]

Love the fact you actually demonstrated these security concepts with code. Thank you! Also for the Broken Object Level Authorization example could we alternatively embed the shopId into the jwt token or cookie as a claim on login then the subsequent requests to the "revenue" endpoint can use this shopId to fetch revenue?

[@Codewrinkles]

Theoretically yes, but that would become more cumbersome when I have more shops. The important idea is that you need to varify that only the shop owner can view the revenue. How you do it, it's up to you. Be creative.

[@asiridissanayaka6849]

Very much practical and well explained.

[@broadshare]

Very practical, thank you.

[@zeeshanasghar3751]

love it, simple and precise

[@Codewrinkles]

Glad you liked it.

[@DeepWorksStudios]

Great content, keep it up!

[@Codewrinkles]

Thank you! I do my best to keep it up :)

[@dotnetdevni]

I have been thinking about this more and more should I be encrypting the payload I always have ssl and all but most of the times im passing jason data.

[@Codewrinkles]

Maybe I'm missing something. The entire request is encrypted. Why also encrypting the payload?

[@matt-irby]

Awesome video!

[@Codewrinkles]

Glad you enjoyed it. Make sure to share it.

[@arunbm123]

❤

[@hifirulezzz]

Security is important, but who is sending id in the header? It is dumb. Token should be created and encrypted during login. Only token contains information for authentication and authorization