Introduction to OAuth 2.0 and OpenID Connect • Philippe De Ryck • GOTO 2018

Поділитися
Вставка
  • Опубліковано 18 січ 2025

КОМЕНТАРІ • 37

  • @PaulVanBladel
    @PaulVanBladel 3 роки тому +11

    Brilliant. There are just talks or there is a presentation driven by someone who has the vast intention and willingness to transfer knowledge. That's what we have here. Thanks Philippe.

  • @leo-phiponacci
    @leo-phiponacci Рік тому +1

    The best talk about OAuth and OIDC ever watched

  • @ubaidullah3328
    @ubaidullah3328 2 роки тому

    Thank you. First talk in two weeks that has explained oidc

  • @vadimemelin2941
    @vadimemelin2941 2 роки тому +2

    Man, I am glad that thing finally makes sense to me

  • @VIJAYBVERMA
    @VIJAYBVERMA 5 років тому +6

    Thank you.
    By far the best session on OAuth2.0 available on youtube.

  • @albpace
    @albpace 5 років тому +6

    Finally an outstanding presentation that also explain the resource server perspective. Without doubt the best Oauth-2 presentation so far I have found on youtube.

  • @islamh6042
    @islamh6042 2 роки тому +1

    A consolidated session. Thanks a lot Philippe and GOTO!

  • @nikolassepos1640
    @nikolassepos1640 4 роки тому +2

    Thank you Philippe De Ryck for this excellent presentation!

  • @maartenknf
    @maartenknf 3 роки тому +2

    This is a really clear explanation!

  • @divabanyuwigara3562
    @divabanyuwigara3562 5 років тому +5

    I like this guy, he explain very well.

  • @sudiptapal7606
    @sudiptapal7606 5 років тому +2

    The best on the topic ! Philipe rocks !

  • @tiwarivikash12
    @tiwarivikash12 5 років тому +2

    Endpoint should be /token instead of /auth at 17:26

  • @TanujitChowdhury
    @TanujitChowdhury 4 роки тому +1

    Really nice explanation on OIDC flow and what to do with the ID token

  • @jailson772
    @jailson772 5 років тому +1

    Awesome explanation thanks Philippe

  • @bipinkhatiwada
    @bipinkhatiwada 5 років тому +2

    that's a very great explanation, man. thanks a lot.

  • @iammen7
    @iammen7 5 років тому +1

    Very good explanation. Thanks you.

  • @mgrycz
    @mgrycz 5 років тому +1

    Perfect presentation.

  • @tibi536
    @tibi536 5 років тому +2

    Outstanding presentation, thank you for sharing!

  • @hackerman5764
    @hackerman5764 2 місяці тому

    In these diagrams, using the Twitter example, would "client" always refer to Buffer's back and and "resource server" always refer to Twitter's back end?

  • @MrOsefosef
    @MrOsefosef Рік тому

    Small but important detail 41:16 he says there are only 3 flows but in reality OpenID Connect supports all OAuth 2.0 grant types including ROPC Grant and Client Credentials Grant.

  • @nullentrophy
    @nullentrophy 3 роки тому +1

    I love GOTO; Intro

  • @baolam4180
    @baolam4180 2 роки тому +1

    Thanks

  • @loginjones
    @loginjones 6 років тому +1

    wonderful talk

  • @daoudacamara5232
    @daoudacamara5232 5 років тому

    Very good presentation!

  • @toriaezunama
    @toriaezunama 6 років тому +3

    Really well explained. Thank you!

  • @Anon-tt9rz
    @Anon-tt9rz 5 років тому

    very well presented, thanks!

  • @jinxblaze
    @jinxblaze 6 років тому +1

    beautiful

  • @nikitarungta3423
    @nikitarungta3423 5 років тому

    very well explained

  • @ThePelcher
    @ThePelcher 5 років тому

    Very good!

  • @acsidaho
    @acsidaho 6 років тому

    very helpful. thank you.

  • @rodolfopicoreti8115
    @rodolfopicoreti8115 5 років тому +1

    Excelent...

  • @tech.talk69
    @tech.talk69 4 роки тому

    Can you give me that What is Client at 14 : 25 ?? Follow me it can Server API ?

  • @ankitsolomon
    @ankitsolomon 6 років тому

    Slides link pls

    • @GOTO-
      @GOTO-  6 років тому +1

      Hi there, thanks for your comment. If available the slides are linked in the video description. Here you go:
      gotober.com/2018/sessions/653

  • @vincentbaeten173
    @vincentbaeten173 4 роки тому

    Too bad he doesn't say anything about the Authorization Code Grant with Proof Key For Code Exchange (PKCE) flow because that is now the recommended flow for public clients instead of the implicit flow. And yes this was recommended before 2018.

  • @sarinnawangkanai7768
    @sarinnawangkanai7768 Рік тому

    Philippe De Ryck