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

Поделиться
HTML-код
  • Опубликовано: 29 янв 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

  • @islamh6042
    @islamh6042 2 года назад +1

    A consolidated session. Thanks a lot Philippe and GOTO!

  • @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.

  • @VIJAYBVERMA
    @VIJAYBVERMA 5 лет назад +6

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

  • @nikolassepos1640
    @nikolassepos1640 4 года назад +2

    Thank you Philippe De Ryck for this excellent presentation!

  • @maartenknf
    @maartenknf 3 года назад +2

    This is a really clear explanation!

  • @sudiptapal7606
    @sudiptapal7606 5 лет назад +2

    The best on the topic ! Philipe rocks !

  • @TanujitChowdhury
    @TanujitChowdhury 4 года назад +1

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

  • @tiwarivikash12
    @tiwarivikash12 5 лет назад +2

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

  • @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?

  • @divabanyuwigara3562
    @divabanyuwigara3562 5 лет назад +5

    I like this guy, he explain very well.

  • @jailson772
    @jailson772 5 лет назад +1

    Awesome explanation thanks Philippe

  • @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.

  • @bipinkhatiwada
    @bipinkhatiwada 5 лет назад +2

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

  • @mgrycz
    @mgrycz 5 лет назад +1

    Perfect presentation.

  • @nullentrophy
    @nullentrophy 3 года назад +1

    I love GOTO; Intro

  • @iammen7
    @iammen7 5 лет назад +1

    Very good explanation. Thanks you.

  • @tibi536
    @tibi536 5 лет назад +2

    Outstanding presentation, thank you for sharing!

  • @daoudacamara5232
    @daoudacamara5232 5 лет назад

    Very good presentation!

  • @baolam4180
    @baolam4180 2 года назад +1

    Thanks

  • @loginjones
    @loginjones 6 лет назад +1

    wonderful talk

  • @tech.talk69
    @tech.talk69 4 года назад

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

  • @Anon-tt9rz
    @Anon-tt9rz 5 лет назад

    very well presented, thanks!

  • @toriaezunama
    @toriaezunama 6 лет назад +3

    Really well explained. Thank you!

  • @jinxblaze
    @jinxblaze 6 лет назад +1

    beautiful

  • @nikitarungta3423
    @nikitarungta3423 5 лет назад

    very well explained

  • @ThePelcher
    @ThePelcher 5 лет назад

    Very good!

  • @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

  • @rodolfopicoreti8115
    @rodolfopicoreti8115 5 лет назад +1

    Excelent...

  • @acsidaho
    @acsidaho 6 лет назад

    very helpful. thank you.

  • @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 2 года назад

    Philippe De Ryck