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 changed one line
[{$pagename}] or (Client Credentials Flow] is a server to server flow. 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).
[{$pagename}] or (Client Credentials Flow] is a server to server using a [Grant_type] of [client_credentials].
At line 7 added 2 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).
At line 16 added 5 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
At line 17 removed one line
The [Authorization Request Parameters] are done in a [HTTP POST] to the [Token_endpoint]
At line 19 removed 4 lines
The Token Endpoint [|https://curity.io/resources/learn/oauth-client-credentials-flow/#the-token-endpoint]