OAuth client credentials flow

preview_player
Показать описание

00:00 What is the OAuth client credentials flow?
00:54 OAuth client credentials walkthrough
03:05 conclusion

The OAuth client credentials flow was primarily designed for machine to machine communication (e.g for service account). It is sometimes also referred to as two-legged OAuth because there is no natural person involved. The idea is that the application exchanges a client id and a secret for an access token. Since no user is sitting in between, it does not make much sense to also request a refresh token. In fact it is even better for the authorization server to not send a refresh token because then access can be more easily revoked if needed.
Рекомендации по теме
Комментарии
Автор

What do you think about this explanation?
Was ist clear?

jgoebel
Автор

"client secret for confidential servers only" Thank you.

deepnoida
Автор

Great short and concise video. Can you make a similar one but this time a deep dive about Client Credential Grant flow using a SSL certificate and making use of Client Assertions. (Instead of client secret)

The benefits with using that.

andreas
Автор

Thank you for a great explanation and same for all your other great tutorials. I would like to ask for the 2 legged OAUTH example. Can the Authorisation server be in the client's realm/ domain? If so, then the resource server (I.e. Google Compute Engine in the example) would need to trust the Authorisation server and validate the Token? Also, we would configure PKCE in any case? Thank you. Tony

bbstriker
Автор

Thanks I was wondering if I should care about a refresh token or not

wardevoidnoodle
Автор

Posting context dependent video tutorials to youtube in small clips isn't the most helpful thing in the world

i.t