This page (revision-7) was last changed on 29-Nov-2024 16:16 by -jim

This page was created on 29-Nov-2024 16:16 by unknown

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
7 29-Nov-2024 16:16 1 KB -jim to previous
6 29-Nov-2024 16:16 1 KB -jim to previous | to last
5 29-Nov-2024 16:16 1 KB -jim to previous | to last
4 29-Nov-2024 16:16 1 KB -jim to previous | to last
3 29-Nov-2024 16:16 1 KB -jim to previous | to last
2 29-Nov-2024 16:16 1 KB -jim to previous | to last
1 29-Nov-2024 16:16 896 bytes unknown to last

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 5 added one line
[{$pagename}] or (Client Credentials Flow) is a server to server using a [Grant_type] of client_credentials.
At line 7 added 7 lines
There is no user [authentication] involved in the process. In fact there is no user at all, the resulting [Access_tokens] will not contain a user, but will instead contain the [Client_id] as subject (if not configured otherwise).
This flow is useful for systems that need to perform [API] operations when no user is present. It can be nightly operations, or other that involve contacting OAuth protected APIs.
Since there is no user authorization, the flow only interacts with the Token endpoint.
At line 16 added 9 lines
The [Client] send the following [Authorization Request Parameters]: (Sent as a [HTTP POST] to the [Token_endpoint])
* client_id
* client_secret
* grant_type: client_credentials
* scope: Space separated string of scopes
[{$pagename}] has no [Refresh_token] is issued. The client can make the same call again to obtain a new access token.
At line 30 added 2 lines
* [#2] - [!!! OAuth Client Credentials Flow
|https://curity.io/resources/learn/oauth-client-credentials-flow/|target='_blank'] - based on information obtained 2022-02-15