The truth about cookies, tokens and APIs - Phillipe de Ryck

Ғылым және технология

With the rise of Single Page Applications, we also see a paradigm shift in session management techniques. Instead of using server-side cookie-based sessions, many developers are shifting towards client-side state mechanisms, using JWT tokens an custom HTTP headers. There’s plenty of conflicting advice out there, discussing cookie security issues, Cross-Site Request Forgery, and XSS. So how can you make a sensible choice, and how will that impact the security of your application?
This talk will guide you in this choice. We dive into the technicalities behind these technologies, and the actual security impact of your choices. We’ll look at compatibility with current web security mechanisms. You will learn how to assess your past choices, and how to substantiate future decisions.
Speaker:
Philippe De Ryck
Pragmatic Web Security
Founder
I am the founder of Pragmatic Web Security, where I travel the world to train developers on web security and security engineering. I hold a Ph.D. in web security from KU Leuven. Google recognizes me as a Google Developer Expert for my knowledge of web security and security in Angular applications. Screen reader support enabled.

Пікірлер: 3

  • @jayshah5695
    @jayshah5695 Жыл бұрын

    Great explaination

  • @parthapal8380
    @parthapal83804 жыл бұрын

    In this presentation Philippe clears a confusing concept of reference token and self contained token flows

  • @hasparus
    @hasparus3 жыл бұрын

    22:50 I don't how hard can it be to send an API's authorization header only to the API that the token belongs to. Couldn't we ignore Angular if it makes stuff so hard? Calling the endpoint with proper headers using Vanilla.js Fetch API is pretty straightforward.

Келесі