Uploaded May 2024 | Updated September 2026, 2 weeks ago
Imagine this: your CLI needs to interact with a protected API but your CLI can’t simply make a request to the API, it first needs an access token. Protected APIs usually have an authorization server responsible for checking credentials and making sure parties trying to access protected resources have indeed the right access.
To get an access token your CLI needs to send the credentials like client ID and client secret to the authorization server, and if the credentials checkout, it gets back an access token enabling your CLI to perform certain actions or access protected endpoints from that API.
All of this happens without human interaction and it is known as client credentials flow. When machine-to-machine applications authenticate and authorize the app rather than a user.
Now you know what client credentials flow is, thanks for watching!
For more content on identity, token based authentication, OAuth, passkeys and more, subscribe to our channel :)
Imagine this: your CLI needs to interact with a protected API but your CLI can’t simply make a request to the API, it first needs an access token. Protected APIs usually have an authorization server responsible for checking credentials and making sure parties trying to access protected resources have indeed the right access.
To get an access token your CLI needs to send the credentials like client ID and client secret to the authorization server, and if the credentials checkout, it gets back an access token enabling your CLI to perform certain actions or access protected endpoints from that API.
All of this happens without human interaction and it is known as client credentials flow. When machine-to-machine applications authenticate and authorize the app rather than a user.
Now you know what client credentials flow is, thanks for watching!
For more content on identity, token based authentication, OAuth, passkeys and more, subscribe to our channel :)
