<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">Am 19.04.2022 um 15:41 schrieb David Chadwick via Openid-specs-ab <<a href="mailto:openid-specs-ab@lists.openid.net" class="">openid-specs-ab@lists.openid.net</a>>:</div><br class="Apple-interchange-newline"><div class="">
  
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" class="">
  
  <div class=""><p class=""><br class="">
    </p>
    <div class="moz-cite-prefix">On 19/04/2022 14:32, Torsten
      Lodderstedt via Openid-specs-ab wrote:<br class="">
    </div>
    <blockquote type="cite" cite="mid:56379E81-DDEF-4B8F-A7C5-D5345F96893E@lodderstedt.net" class="">
      <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 class=""><br class="">
      </div>
      I assume it would ignore unknown claims, like any other OIDC OP. <br class="">
    </blockquote><p class="">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 class="">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><div class=""><br class=""></div></div></div></blockquote><div><br class=""></div>That’s certainly an option. But the user might also decide to proceed and use other means (!= the wallet) to provide the RP with the requested data.</div><div><br class=""></div><div><blockquote type="cite" class=""><div class=""><div class=""><p class="">Kind regards</p><p class="">David<br class="">
    </p>
  </div>

_______________________________________________<br class="">Openid-specs-ab mailing list<br class=""><a href="mailto:Openid-specs-ab@lists.openid.net" class="">Openid-specs-ab@lists.openid.net</a><br class="">https://lists.openid.net/mailman/listinfo/openid-specs-ab<br class=""></div></blockquote></div><br class=""></body></html>