<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><br>
</p>
<div class="moz-cite-prefix">On 19/04/2022 14:32, Torsten
Lodderstedt via Openid-specs-ab wrote:<br>
</div>
<blockquote type="cite"
cite="mid:56379E81-DDEF-4B8F-A7C5-D5345F96893E@lodderstedt.net">
<blockquote type="cite" class="">
<div class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space;
line-break: after-white-space;" class="">
<div class="">
<blockquote type="cite" class="">
<div class="">
<div dir="ltr" class="">4. What if self-asserted
claims are sufficient but the SIOP wallet doesn't
support the required requested claim in the
authentication request?</div>
</div>
</blockquote>
<div class=""><br class="">
</div>
<div class="">I don’t entirely understand this question,
sorry.</div>
</div>
</div>
</div>
</blockquote>
<div><br class="">
</div>
I assume it would ignore unknown claims, like any other OIDC OP. <br>
</blockquote>
<p>I don't think this will work. The RP is most likely to reject the
user that does not have the required claims. The only way unknown
claims can work is if they are contained in a disjunctive request
in which the other option contains claims that are known e.g. send
<RP's proprietary unknown claim> or <government ID>.</p>
<p>So if the SIOP wallet does not support the required requested
claim(s) the user should be told that connection is not possible
until <unknown claim(s)> is(are) obtained.</p>
<p>Kind regards</p>
<p>David<br>
</p>
</body>
</html>