Skip to content

Commit 488ae28

Browse files
authored
Merge pull request #6 from openid/mbj-implementation-considerations
Merging, per decision on the 24-Apr-25 working group call.
2 parents 549f01c + e968e2c commit 488ae28

File tree

1 file changed

+35
-2
lines changed

1 file changed

+35
-2
lines changed

openid-connect-rp-metadata-choices-1_0.xml

Lines changed: 35 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@
5757
</address>
5858
</author>
5959

60-
<date day="21" month="April" year="2025" />
60+
<date day="24" month="April" year="2025" />
6161

6262
<workgroup>OpenID Connect Working Group</workgroup>
6363

@@ -416,6 +416,33 @@
416416
</t>
417417
</section>
418418

419+
<section anchor="ImplementationConsiderations" title="Implementation Considerations">
420+
<t>
421+
To facilitate interoperability with implementations not supporting
422+
this specification, deployments SHOULD include
423+
the single-valued metadata parameter alongside
424+
the corresponding multi-valued metadata parameter with their
425+
preferred single value.
426+
</t>
427+
<t>
428+
This preference is particularly important in the case when
429+
the Authorization Server does not support the single-valued parameter value.
430+
For instance, consider these metadata values:
431+
<figure>
432+
<artwork><![CDATA[
433+
"id_token_signing_alg_values_supported": ["ES256", "PS256", "RS256"],
434+
"id_token_signed_response_alg": "RS256"
435+
]]></artwork>
436+
</figure>
437+
</t>
438+
<t>
439+
Authorization Server SHOULD NOT consider it an error when it doesn't support
440+
<spanx style="verb">RS256</spanx> if it supports either of the other choices
441+
<spanx style="verb">ES256</spanx> or <spanx style="verb">PS256</spanx>.
442+
It SHOULD use one of the choices that it does support, or reject the registration with the <spanx style="verb">invalid_client_metadata</spanx> error when none of the client-provided values are supported.
443+
</t>
444+
</section>
445+
419446
<section anchor="Security" title="Security Considerations">
420447
<t>
421448
The security considerations when using these metadata parameters
@@ -1117,7 +1144,7 @@
11171144

11181145
<t>
11191146
-02
1120-
<list style="symbols">
1147+
<list style="symbols">
11211148
<t>
11221149
Added multi-valued metadata parameters based on single-valued metadata parameters
11231150
in <xref target="CIBA.Core"/>, <xref target="JARM"/>, and <xref target="RFC9701"/>.
@@ -1128,6 +1155,11 @@
11281155
<t>
11291156
Added Filip Skokan as an author.
11301157
</t>
1158+
<t>
1159+
Added Implementation Considerations about including
1160+
the single-valued metadata parameter alongside
1161+
the corresponding multi-valued metadata parameter.
1162+
</t>
11311163
</list>
11321164
</t>
11331165

@@ -1158,6 +1190,7 @@
11581190
The authors wish to acknowledge the contributions of the following
11591191
people to this specification:
11601192
Vladimir Dzhuvinov,
1193+
Michael Fraser,
11611194
Joseph Heenan,
11621195
and
11631196
Stefan Santesson.

0 commit comments

Comments
 (0)