Skip to content

Commit 023e5e6

Browse files
authored
Merge pull request #187 from selfissued/mbj-passing-request-objects
Request Objects can be passed by value or by reference
2 parents fc26eb9 + c90c0ce commit 023e5e6

File tree

1 file changed

+5
-2
lines changed

1 file changed

+5
-2
lines changed

openid-federation-1_0.xml

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5798,9 +5798,9 @@ Content-Type: application/json
57985798
<section anchor="authn-request" title="Authentication Request">
57995799
<t>
58005800
The Authentication Request is performed by passing a
5801-
signed Request Object by value as described in Section 6.1 of
5801+
Request Object by value or by reference, as described in Section 6 of
58025802
<xref target="OpenID.Core">OpenID Connect Core 1.0</xref>
5803-
and <xref target="RFC9101">The OAuth 2.0 Authorization Framework: JWT-Secured Authorization Request (JAR)</xref>
5803+
and <xref target="RFC9101">The OAuth 2.0 Authorization Framework: JWT-Secured Authorization Request (JAR)</xref>,
58045804
or using a pushed authorization request, as described in
58055805
<xref target="RFC9126">Pushed Authorization Requests</xref>.
58065806
</t>
@@ -10045,6 +10045,9 @@ Host: op.umu.se
1004510045
<t>
1004610046
-42
1004710047
<list style="symbols">
10048+
<t>
10049+
Fixed #184: Clarified that Request Objects can be passed by value or by reference.
10050+
</t>
1004810051
<t>
1004910052
Fixed #178: Clarify that other client methods (than automatic and explicit) are allowed.
1005010053
</t>

0 commit comments

Comments
 (0)