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

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

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
5 29-Nov-2024 16:16 1 KB Administrator to previous
4 29-Nov-2024 16:16 1 KB Administrator to previous | to last
3 29-Nov-2024 16:16 1 KB Administrator to previous | to last
2 29-Nov-2024 16:16 1 KB Administrator to previous | to last
1 29-Nov-2024 16:16 1 KB Administrator to last

Page References

Incoming links Outgoing links
Pushed Authorization Requests
Pushed Authorization Requests

Version management

Difference between version and

At line 2 changed one line
[{$pagename}] is defined in [RFC 9126] and defines the [{$pagename}] ([PAR]) [endpoint], which allows [OAuth Clients] to [push|HTTP POST] the payload of an OAuth 2.0 [Authorization Request] to the [Authorization Server] via a direct request and provides them with a [request] [URI] that is used as reference to the data in a subsequent call to the [Authorization_endpoint].
[{$pagename}] is defined in [RFC 9126] and defines the [{$pagename}] ([PAR]) [endpoint], which allows [OAuth Clients] to [push] the payload of an OAuth 2.0 [Authorization Request] to the [Authorization Server] via a direct request and provides them with a [request] [URI] that is used as reference to the data in a subsequent call to the [Authorization_endpoint].
At line 6 changed one line
[OAuth 2.0 JWT Secured Authorization Request] ([JAR]) [RFC 9101] provides solutions for the security challenges by allowing [OAuth Clients] to wrap [Authorization Request] parameters in a Request Object, which is a signed and optionally encrypted [JSON Web Token] ([JWT]) [RFC 7519]. In order to cope with the size restrictions, [JAR] introduces the request_uri parameter that allows [OAuth Clients] to send a reference to a Request Object instead of the Request Object itself.
[JWT-Secured Authorization Request] ([JAR]) [RFC 9101] provides solutions for the security challenges by allowing [OAuth Clients] to wrap [Authorization Request] parameters in a Request Object, which is a signed and optionally encrypted [JSON Web Token] ([JWT]) [RFC 7519]. In order to cope with the size restrictions, [JAR] introduces the request_uri parameter that allows [OAuth Clients] to send a reference to a Request Object instead of the Request Object itself.
At line 10 removed 4 lines
[{$pagename}] used in [FAPI] and was defined as [FAPI Pushed Request Object].
[{$pagename}] uses the [HTTP POST] to the [Authorization Server]
At line 17 removed 4 lines
----
* [#1] - [RFC 9126|RFC:9126|target='_blank'] - based on information obtained 2022-03-19
* [#2] - [Pushed Authorization Requests (PAR)
|https://curity.io/resources/learn/pushed-authorization-requests/|target='_blank'] - based on information obtained 2022-03-19
This page (revision-5) was last changed on 29-Nov-2024 16:16 by AdministratorTop