<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">Hello Mike,<div><br></div><div>I struggle to see these as metadata that the AS is meant to respond with to a DCR request. </div><div><br></div><div>I understand the intention of allowing the client to say "here's what I support, you choose for me". What I don't get is why the client can't figure out what to use exactly based on the AS metadata in the first place. I must be surely missing something so apologies there. </div><div><br></div><div>Nevertheless I don't think the AS should ever have the need to respond with these metadata in a DCR enpoint response. So, they might be useful as input but don't make much sense in responses to me.</div><div><br id="lineBreakAtBeginningOfSignature"><div dir="ltr">- Filip</div><div dir="ltr"><br><blockquote type="cite">9. 10. 2024 v 4:35, Michael Jones via Openid-specs-ab <openid-specs-ab@lists.openid.net>:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr">
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style>@font-face { font-family: "Cambria Math"; }
@font-face { font-family: Calibri; }
@font-face { font-family: Aptos; }
p.MsoNormal, li.MsoNormal, div.MsoNormal { margin: 0in; font-size: 11pt; font-family: Aptos, sans-serif; }
a:link, span.MsoHyperlink { color: rgb(70, 120, 134); text-decoration: underline; }
span.EmailStyle20 { font-family: Aptos, sans-serif; color: windowtext; }
.MsoChpDefault { font-size: 10pt; }
@page WordSection1 { size: 8.5in 11in; margin: 1in; }
div.WordSection1 { page: WordSection1; }</style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal">The authors of the attached specification hereby contribute it to the OpenID Connect working group. It was created to address issues
<a href="https://bitbucket.org/openid/connect/issues/2158/metadata-parameter-value-arrays-for-rp">
https://bitbucket.org/openid/connect/issues/2158/metadata-parameter-value-arrays-for-rp</a> and
<a href="https://github.com/openid/federation/issues/12">https://github.com/openid/federation/issues/12</a>.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> -- Mike<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-family:"Calibri",sans-serif;mso-ligatures:none">From:</span></b><span style="font-family:"Calibri",sans-serif;mso-ligatures:none"> Michael Jones
<br>
<b>Sent:</b> Thursday, October 3, 2024 10:09 PM<br>
<b>To:</b> openid-specs-ab@lists.openid.net<br>
<b>Subject:</b> FW: OpenID Connect Relying Party Metadata Choices 1.0 spec<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">On Monday’s working group call, we discussed that I should go through the list of
<a href="https://www.iana.org/assignments/oauth-parameters/oauth-parameters.xhtml#client-metadata">
registered OAuth Client Metadata values</a> and see if there were any more that should be added to the list in this specification. My conclusion was that there were not. I’ll therefore plan to contribute it to the working group as-is so we can start addressing
the issues filed unless I hear feedback soon requesting changes first.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> Thanks all,<o:p></o:p></p>
<p class="MsoNormal"> -- Mike<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-family:"Calibri",sans-serif;mso-ligatures:none">From:</span></b><span style="font-family:"Calibri",sans-serif;mso-ligatures:none"> Michael Jones
<br>
<b>Sent:</b> Sunday, September 29, 2024 7:53 PM<br>
<b>To:</b> <a href="mailto:openid-specs-ab@lists.openid.net">openid-specs-ab@lists.openid.net</a><br>
<b>Subject:</b> OpenID Connect Relying Party Metadata Choices 1.0 spec<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The attached spec (with source and HTML output) defines client metadata parameters corresponding to all the single-valued OpenID Connect Dynamic Client Registration metadata parameters, letting RPs declare the sets of values for these parameters
that they support. This is intended to address both <a href="https://bitbucket.org/openid/connect/issues/2158/metadata-parameter-value-arrays-for-rp">
https://bitbucket.org/openid/connect/issues/2158/metadata-parameter-value-arrays-for-rp</a> and
<a href="https://github.com/openid/federation/issues/12">https://github.com/openid/federation/issues/12</a>.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Reviews welcomed!<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> -- Mike<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div><openid-connect-rp-metadata-choices-1_0.xml></div><div><openid-connect-rp-metadata-choices-1_0.html></div><span>_______________________________________________</span><br><span>Openid-specs-ab mailing list</span><br><span>Openid-specs-ab@lists.openid.net</span><br><span>https://lists.openid.net/mailman/listinfo/openid-specs-ab</span><br></div></blockquote></div></body></html>