Protecting Your APIs with OAuth

Поділитися
Вставка
  • Опубліковано 20 жов 2024

КОМЕНТАРІ • 9

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

    Hi Aaron you've mention in various videos about SPA's and JS/Angular apps hosted on CDN's that they should use Auth Code + PKCE. But theres no "back channel" for SPA's. Does this mean front channel will be used? Apart from getting the token by a POST rather than fragment or queryString, are there any other advantages in Auth Code over Implicit?

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

    loved it thanks for the explanation.

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

    My cats love Oauth 2.0 !

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

    I have a hard time separating idToken and accessToken, can you help me with the following:
    The token shown in the video at ua-cam.com/video/8c1SOuO4mPc/v-deo.html, includes both a userId and access scopes.
    Am I right to say that a token which both includes the userId and access scopes is an "idToken"?
    (Cause pure oauth access_tokens only include scopes but no user info)

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

      Access token authorizes access to some server resources. They are not intended to carry information about the user. They simply allow access to certain defined server resources.
      ID token contains information about a user and their authentication status. It can be used by your client both for authentication and as a store of information about that user.

  • @codedynamics1
    @codedynamics1 3 роки тому

    thanks Arron, ive subbed ;)

  • @samanthaferguson6018
    @samanthaferguson6018 3 роки тому

    01:59 spec like legal contract

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

    01:59 spec like legal contract