<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">I don’t think it’s clear whether the intent was an errata or a proposal to the WG to further constrain the Connect certification profile. <div><br></div><div>I believe we could only do the latter. <br><br><div dir="ltr">Odesláno z iPhonu</div><div dir="ltr"><br><blockquote type="cite">17. 1. 2020 v 22:05, Brian Campbell via Openid-specs-fapi <openid-specs-fapi@lists.openid.net>:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><div dir="ltr">For better or worse JOSE allowed for duplicate kids and Connect didn't constrain it. So requiring uniqueness is a breaking change that an erratum shouldn't be doing. I guess that counts as a negative opinion towards the decision in <a href="https://bitbucket.org/openid/connect/issues/1127" target="_blank">https://bitbucket.org/openid/connect/issues/1127</a> <br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Jan 17, 2020 at 12:50 AM Joseph Heenan via Openid-specs-fapi <<a href="mailto:openid-specs-fapi@lists.openid.net">openid-specs-fapi@lists.openid.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="overflow-wrap: break-word;">Hi all,<div><br></div><div>I wanted to direct the FAPI working group to this discussion within the Connect working group:</div><div><br></div><div><a href="https://bitbucket.org/openid/connect/issues/1127" target="_blank">https://bitbucket.org/openid/connect/issues/1127</a></div><div><br></div><div>Namely that duplicate kids are not permitted in JWKS.</div><div><br></div><div>A test for this was recently added to all the conformance tests, which caused one of the UK banks to opine:</div><div><br></div><div><blockquote type="cite">it is valid for the JWK endpoint to return multiple KID instances, one for each ‘alg’ supported?<br>The spec calls for the alg PS256 or longer to be supported, so we also have (for instance) PS384, PS512. And although we may show a couple that we don’t need, my point is that it must be valid to show multiple key entries to support multiple valid alg values. <br></blockquote><br></div><div>To some extent this seems a reasonable point, reusing a key across across two algs that can use the same key seems ok, and arguably perhaps better than having the key once without an ‘alg’ specified.</div><div><br></div><div>As this affects the FAPI certification tests, I wanted to check the FAPI WG agrees with the decision in <a href="https://bitbucket.org/openid/connect/issues/1127" target="_blank">https://bitbucket.org/openid/connect/issues/1127</a> - any opinions (positive & negative) would be great please.</div><div><br></div><div>Thanks</div><div><br></div><div>Joseph Heenan</div><div>OpenID Certification Team</div><div><br></div><div><br></div></div>_______________________________________________<br>
Openid-specs-fapi mailing list<br>
<a href="mailto:Openid-specs-fapi@lists.openid.net" target="_blank">Openid-specs-fapi@lists.openid.net</a><br>
<a href="http://lists.openid.net/mailman/listinfo/openid-specs-fapi" rel="noreferrer" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs-fapi</a><br>
</blockquote></div>
<br>
<i style="margin:0px;padding:0px;border:0px;outline:0px;vertical-align:baseline;background:rgb(255,255,255);font-family:proxima-nova-zendesk,system-ui,-apple-system,system-ui,"Segoe UI",Roboto,Oxygen-Sans,Ubuntu,Cantarell,"Helvetica Neue",Arial,sans-serif;color:rgb(85,85,85)"><span style="margin:0px;padding:0px;border:0px;outline:0px;vertical-align:baseline;background:transparent;font-family:proxima-nova-zendesk,system-ui,-apple-system,BlinkMacSystemFont,"Segoe UI",Roboto,Oxygen-Sans,Ubuntu,Cantarell,"Helvetica Neue",Arial,sans-serif;font-weight:600"><font size="2">CONFIDENTIALITY NOTICE: This email may contain confidential and privileged material for the sole use of the intended recipient(s). Any review, use, distribution or disclosure by others is strictly prohibited. If you have received this communication in error, please notify the sender immediately by e-mail and delete the message and any file attachments from your computer. Thank you.</font></span></i><span>_______________________________________________</span><br><span>Openid-specs-fapi mailing list</span><br><span>Openid-specs-fapi@lists.openid.net</span><br><span>http://lists.openid.net/mailman/listinfo/openid-specs-fapi</span><br></div></blockquote></div></body></html>