This page (revision-2) 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
2 29-Nov-2024 16:16 748 bytes -jim to previous
1 29-Nov-2024 16:16 757 bytes unknown to last

Page References

Incoming links Outgoing links
Token_endpoint
Token_endpoint

Version management

Difference between version and

At line 2 changed 3 lines
[{$pagename}] is the [OAuth 2.0 Endpoint] on the [Authorization Server] where the [OAuth Client] exchanges the [Authorization Grant], [client_id] and [Client Secret], for an [Access Token] by submission of [Access Token Request].
To obtain an [Access Token], an [OpenID Connect] [Identity Token], and optionally a [Refresh Token], the [OAuth Client] sends a Token Request to the [{$pagename}] to obtain a [Access Token Response], as described in Section 3.2 of [OAuth 2.0] [RFC 6749], when using the [Authorization Code Flow].
[{$pagename}] is the [OAuth 2.0 Endpoint] on the [Authorization Server] where the [OAuth Client] exchanges the [Authorization Grant], [client_id] and [Client Secret], for an [Access Token] by submission of [Access Token Request].To obtain an [Access Token], an [OpenID Connect] [Identity Token], and optionally a [Refresh Token], the [OAuth Client] sends a Token Request to the [{$pagename}] to obtain a [Access Token Response], as described in Section 3.2 of [OAuth 2.0] [RFC 6749], when using the [Authorization Code Flow].
This page (revision-2) was last changed on 29-Nov-2024 16:16 by -jimTop