<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Using X.500 CAs as an example, if an erroneous request for a PKC
is sent to the CA, the CA is entitled to correct the information
and send back the correct information in the issued PKC. So if the
issuer knows what the correct name of the VC subject is, it could
return the VC with the correct name in the subject field. After
all, the issuer is asserting the truth as it knows it to be. The
holder can always reject the VC if it does not like the values
that have been inserted by the issuer, but it cannot require the
issuer to insert false values. There is no requirement on the
holder to hold any VCs that it receives from the issuer or to
present them to any verifier.</p>
<p>Kind regards</p>
<p>David<br>
</p>
<div class="moz-cite-prefix">On 29/09/2023 16:07, Joseph Heenan via
Openid-specs-ab wrote:<br>
</div>
<blockquote type="cite"
cite="mid:C1F01749-CC0F-4E82-A2BD-87000F6E3580@authlete.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
Hi Kai
<div><br>
</div>
<div>I’m not sure any of these cases are really strictly defined.
Certainly we don’t test any behaviours like this in any of the
OpenID Foundation conformance tests, although the testing of the
claims perhaps is certainly not comprehensive.</div>
<div><br>
</div>
<div>Rejecting the request seems fine.</div>
<div><br>
</div>
<div>Accepting the request but ignoring parts of it is probably
acceptable as I can’t see anything that really defines the
behaviour in this case. You should probably NOT return any
claims where the request for that claim is invalid. The caveat
would be that by ignoring that part of the request you’re also
losing your ability to tell the developer why their request is
not working as they expected, which makes it harder for them to
figure out what they’ve done wrong and hence harder for them to
fix their request to be valid.</div>
<div><br>
</div>
<div>In reality we really shouldn’t be expecting a situation like
this to occur except when a developer has badly misread the
specification, and hence my instinct is we should err towards
returning an error that tells the developer what they’ve done
wrong.</div>
<div><br>
</div>
<div>(For clarity the above is not an official position of the
OpenID Foundation.)</div>
<div><br>
</div>
<div>Thanks</div>
<div><br>
</div>
<div>Joseph</div>
<div><br>
<div><br>
<blockquote type="cite">
<div>On 28 Sep 2023, at 14:06, Kai Lehmann via
Openid-specs-ab <a class="moz-txt-link-rfc2396E" href="mailto:openid-specs-ab@lists.openid.net"><openid-specs-ab@lists.openid.net></a>
wrote:</div>
<br class="Apple-interchange-newline">
<div>
<meta charset="UTF-8">
<div class="WordSection1"
style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;">
<div
style="margin: 0cm; font-size: 11pt; font-family: Calibri, sans-serif;"><span
lang="EN-US">Hi,<o:p></o:p></span></div>
<div
style="margin: 0cm; font-size: 11pt; font-family: Calibri, sans-serif;"><span
lang="EN-US"><o:p> </o:p></span></div>
<div
style="margin: 0cm; font-size: 11pt; font-family: Calibri, sans-serif;"><span
lang="EN-US">The OIDCC spec allows RPs to request
individual claims with the claims parameter:<o:p></o:p></span></div>
<div
style="margin: 0cm; font-size: 11pt; font-family: Calibri, sans-serif;"><span
lang="EN-US"><o:p> </o:p></span></div>
<div
style="margin: 0cm; font-size: 11pt; font-family: Calibri, sans-serif;"><span
lang="EN-US"><a
href="https://openid.net/specs/openid-connect-core-1_0.html#IndividualClaimsRequests"
style="color: rgb(5, 99, 193); text-decoration: underline;"
moz-do-not-send="true"
class="moz-txt-link-freetext">https://openid.net/specs/openid-connect-core-1_0.html#IndividualClaimsRequests</a><o:p></o:p></span></div>
<div
style="margin: 0cm; font-size: 11pt; font-family: Calibri, sans-serif;"><span
lang="EN-US"><o:p> </o:p></span></div>
<div
style="margin: 0cm; font-size: 11pt; font-family: Calibri, sans-serif;"><span
lang="EN-US">I was wondering how strict the OP
should be in handling invalid claim values within
this request. For example:<o:p></o:p></span></div>
<div
style="margin: 0cm; font-size: 11pt; font-family: Calibri, sans-serif;"><span
lang="EN-US"><o:p> </o:p></span></div>
<div
style="margin: 0cm; font-size: 11pt; font-family: Calibri, sans-serif;"><span
lang="EN-US">{<o:p></o:p></span></div>
<div
style="margin: 0cm; font-size: 11pt; font-family: Calibri, sans-serif;"><span
lang="EN-US"> “first_name”: “INVALID”,<o:p></o:p></span></div>
<div
style="margin: 0cm; font-size: 11pt; font-family: Calibri, sans-serif;"><span
lang="EN-US"> “last_name”: 5,<o:p></o:p></span></div>
<div
style="margin: 0cm; font-size: 11pt; font-family: Calibri, sans-serif;"><span
lang="EN-US"> “email”: {<o:p></o:p></span></div>
<div
style="margin: 0cm; font-size: 11pt; font-family: Calibri, sans-serif;"><span
lang="EN-US"> “essential”: “INVALID”<o:p></o:p></span></div>
<div
style="margin: 0cm; font-size: 11pt; font-family: Calibri, sans-serif;"><span
lang="EN-US"> }<o:p></o:p></span></div>
<div
style="margin: 0cm; font-size: 11pt; font-family: Calibri, sans-serif;"><span
lang="EN-US">}<o:p></o:p></span></div>
<div
style="margin: 0cm; font-size: 11pt; font-family: Calibri, sans-serif;"><span
lang="EN-US"><o:p> </o:p></span></div>
<div
style="margin: 0cm; font-size: 11pt; font-family: Calibri, sans-serif;"><span
lang="EN-US">My interpretation of “The member values
MUST be one of the following …” would be that the
claims request parameter would be invalid if it
contained invalid member values and thus the server
should reject the request with a redirect back to
the RP’s provided redirect_uri with invalid_request
error. Would a more relaxed parsing (ignoring
invalid claim parameters) also be an option and
still in accordance with the specification?<o:p></o:p></span></div>
<div
style="margin: 0cm; font-size: 11pt; font-family: Calibri, sans-serif;"><span
lang="EN-US"><o:p> </o:p></span></div>
<div
style="margin: 0cm; font-size: 11pt; font-family: Calibri, sans-serif;"><span
lang="EN-US">Best regards,<o:p></o:p></span></div>
<div
style="margin: 0cm; font-size: 11pt; font-family: Calibri, sans-serif;"><span
lang="EN-US">Kai<o:p></o:p></span></div>
<div
style="margin: 0cm; font-size: 11pt; font-family: Calibri, sans-serif;"><span
lang="EN-US"><o:p> </o:p></span></div>
</div>
<span
style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;">_______________________________________________</span><br
style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;">
<span
style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;">Openid-specs-ab
mailing list</span><br
style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;">
<a href="mailto:Openid-specs-ab@lists.openid.net"
style="color: rgb(5, 99, 193); text-decoration: underline; font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"
moz-do-not-send="true" class="moz-txt-link-freetext">Openid-specs-ab@lists.openid.net</a><br
style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;">
<a
href="https://lists.openid.net/mailman/listinfo/openid-specs-ab"
style="color: rgb(5, 99, 193); text-decoration: underline; font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"
moz-do-not-send="true" class="moz-txt-link-freetext">https://lists.openid.net/mailman/listinfo/openid-specs-ab</a></div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Openid-specs-ab mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Openid-specs-ab@lists.openid.net">Openid-specs-ab@lists.openid.net</a>
<a class="moz-txt-link-freetext" href="https://lists.openid.net/mailman/listinfo/openid-specs-ab">https://lists.openid.net/mailman/listinfo/openid-specs-ab</a>
</pre>
</blockquote>
<pre class="moz-signature" cols="72">--
IMPORTANT NOTICE
The email addresses ..@verifiablecredentials.info will shortly stop working.
Can you please use
<a class="moz-txt-link-abbreviated" href="mailto:d.w.chadwick@truetrust.co.uk">d.w.chadwick@truetrust.co.uk</a>
from now on</pre>
</body>
</html>