|
57 | 57 | </address> |
58 | 58 | </author> |
59 | 59 |
|
60 | | - <date day="21" month="April" year="2025" /> |
| 60 | + <date day="24" month="April" year="2025" /> |
61 | 61 |
|
62 | 62 | <workgroup>OpenID Connect Working Group</workgroup> |
63 | 63 |
|
|
416 | 416 | </t> |
417 | 417 | </section> |
418 | 418 |
|
| 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 | + |
419 | 446 | <section anchor="Security" title="Security Considerations"> |
420 | 447 | <t> |
421 | 448 | The security considerations when using these metadata parameters |
|
1117 | 1144 |
|
1118 | 1145 | <t> |
1119 | 1146 | -02 |
1120 | | - <list style="symbols"> |
| 1147 | + <list style="symbols"> |
1121 | 1148 | <t> |
1122 | 1149 | Added multi-valued metadata parameters based on single-valued metadata parameters |
1123 | 1150 | in <xref target="CIBA.Core"/>, <xref target="JARM"/>, and <xref target="RFC9701"/>. |
|
1128 | 1155 | <t> |
1129 | 1156 | Added Filip Skokan as an author. |
1130 | 1157 | </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> |
1131 | 1163 | </list> |
1132 | 1164 | </t> |
1133 | 1165 |
|
|
1158 | 1190 | The authors wish to acknowledge the contributions of the following |
1159 | 1191 | people to this specification: |
1160 | 1192 | Vladimir Dzhuvinov, |
| 1193 | + Michael Fraser, |
1161 | 1194 | Joseph Heenan, |
1162 | 1195 | and |
1163 | 1196 | Stefan Santesson. |
|
0 commit comments