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

Поделиться
HTML-код
  • Опубликовано: 26 авг 2024

Комментарии • 14

  • @Tolmachovtv
    @Tolmachovtv 5 месяцев назад

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

  • @asiridissanayaka6849
    @asiridissanayaka6849 3 месяца назад

    Very much practical and well explained.

  • @broadshare
    @broadshare 4 месяца назад

    Very practical, thank you.

  • @uzayrsyed6293
    @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
      @Codewrinkles  Год назад +1

      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.

  • @zeeshanasghar3751
    @zeeshanasghar3751 Год назад +1

    love it, simple and precise

  • @DeepWorksStudios
    @DeepWorksStudios Год назад

    Great content, keep it up!

    • @Codewrinkles
      @Codewrinkles  Год назад

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

  • @matt-irby
    @matt-irby Год назад

    Awesome video!

    • @Codewrinkles
      @Codewrinkles  Год назад

      Glad you enjoyed it. Make sure to share it.

  • @dotnetdevni
    @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
      @Codewrinkles  Год назад

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

  • @hifirulezzz
    @hifirulezzz Год назад +1

    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