<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
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]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Spec Call Notes 12-Apr-21<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Mike Jones<o:p></o:p></p>
<p class="MsoNormal">Tony Nadalin<o:p></o:p></p>
<p class="MsoNormal">John Bradley<o:p></o:p></p>
<p class="MsoNormal">Kristina Yasuda<o:p></o:p></p>
<p class="MsoNormal">Adam Lemmon<o:p></o:p></p>
<p class="MsoNormal">Tom Jones<o:p></o:p></p>
<p class="MsoNormal">Tim Cappalli<o:p></o:p></p>
<p class="MsoNormal">Jeremie Miller<o:p></o:p></p>
<p class="MsoNormal">Vittorio Bertocci<o:p></o:p></p>
<p class="MsoNormal">Dmitri Zagidulin<o:p></o:p></p>
<p class="MsoNormal">Edmund Jay<o:p></o:p></p>
<p class="MsoNormal">David Waite (DW)<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Logout Issues<o:p></o:p></p>
<p class="MsoNormal"> <a href="https://bitbucket.org/openid/connect/issues?status=new&status=open&component=Logout">
https://bitbucket.org/openid/connect/issues?status=new&status=open&component=Logout</a><o:p></o:p></p>
<p class="MsoNormal"> 1184: Unclear what to do if id_token_hint user does not match currently logged in user at OP<o:p></o:p></p>
<p class="MsoNormal"> Agreed that since logout is idempotent, that repeating a logout is a success<o:p></o:p></p>
<p class="MsoNormal"> 1216: query over rp initiated logout certification test outcomes for tests that use invalid information<o:p></o:p></p>
<p class="MsoNormal"> Edmund said there's not much point in showing an error, since there's not much the user can do<o:p></o:p></p>
<p class="MsoNormal"> 1183: Handling errors during OpenID Connect RP-Initiated Logout<o:p></o:p></p>
<p class="MsoNormal"> Edmund will add a comment to this one as well<o:p></o:p></p>
<p class="MsoNormal"> 1185: Mention of POST requests and SameSite cookie attributes (RP Initiated Logout)<o:p></o:p></p>
<p class="MsoNormal"> Vittorio said that browsers will flag cross-origin posts served by JavaScript from another origin<o:p></o:p></p>
<p class="MsoNormal"> We could use cookies marked as "none", rather than lax<o:p></o:p></p>
<p class="MsoNormal"> Or we could do a GET with a 302 to itself - an approach that DW said that Ping is using<o:p></o:p></p>
<p class="MsoNormal"> Vittorio agreed to send Mike a description to add to the issue<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Discussing sending VC objects as claims<o:p></o:p></p>
<p class="MsoNormal"> Mike, Kristina, and Oliver wrote <a href="https://openid.bitbucket.io/connect/jwt-claims-for-vc-objects-1_0.html">
https://openid.bitbucket.io/connect/jwt-claims-for-vc-objects-1_0.html</a> to foster discussion<o:p></o:p></p>
<p class="MsoNormal"> DW said that the security considerations for JSON-LD are more complicated than pure JSON<o:p></o:p></p>
<p class="MsoNormal"> It brings back of the complexities we jettisoned with XML DSIG<o:p></o:p></p>
<p class="MsoNormal"> He asked about ignoring not-understood claims<o:p></o:p></p>
<p class="MsoNormal"> He said that we could use _claim_sources for VPs<o:p></o:p></p>
<p class="MsoNormal"> Tony said that we already have "vp" and "vc" claims<o:p></o:p></p>
<p class="MsoNormal"> The processing rules of those are defined by the W3C VC spec - and they're JSON-LD<o:p></o:p></p>
<p class="MsoNormal"> OpenID Connect defines processing rules for some claims, such as "iss", "aud", etc.<o:p></o:p></p>
<p class="MsoNormal"> Jeremie said that you can't take a general JWT and also make it a VC or VP<o:p></o:p></p>
<p class="MsoNormal"> Kristina said that the "vp" and "vc" claims are to embed VC-specific context in their JWT representations<o:p></o:p></p>
<p class="MsoNormal"> DW reported that the entire JWT using "vp" or "vc" is the VP or VC - not just that in the contained claim<o:p></o:p></p>
<p class="MsoNormal"> He also brought up "alg":"none" issues introduced by the W3C spec<o:p></o:p></p>
<p class="MsoNormal"> He said that embedding those claims in an ID Token would change the security properties of an ID Token<o:p></o:p></p>
<p class="MsoNormal"> Dmitri Zagidulin said that there are implementations that stuff entire VPs and VCs into JWTs<o:p></o:p></p>
<p class="MsoNormal"> But they use different claim names, so they're compliant<o:p></o:p></p>
<p class="MsoNormal"> DW reported that we could have _claim_sources=(source type), rather than declaring new IANA JWT claims<o:p></o:p></p>
<p class="MsoNormal"> He said that we need to think about both the presentation and holder cases<o:p></o:p></p>
<p class="MsoNormal"> DW said that he'll be submitting something on this topic soon<o:p></o:p></p>
<p class="MsoNormal"> Dmitri said that some people are embedding objects<o:p></o:p></p>
<p class="MsoNormal"> And they are requesting "vp" and "vc" as custom claims<o:p></o:p></p>
<p class="MsoNormal"> Tim showed an example of how Microsoft is doing that that also uses Presentation Exchange<o:p></o:p></p>
<p class="MsoNormal"> In that case, it truly is layered<o:p></o:p></p>
<p class="MsoNormal"> Kristina also spoke to the layering<o:p></o:p></p>
<p class="MsoNormal"> Findings of Fact:<o:p></o:p></p>
<p class="MsoNormal"> The W3C imposes processing rules on JWT claims for its JWT representations<o:p></o:p></p>
<p class="MsoNormal"> It is possible to completely embed W3C VC-defined objects as claim values<o:p></o:p></p>
<p class="MsoNormal"> DW would like to explore using _claim_sources as Verifiable Presentations<o:p></o:p></p>
<p class="MsoNormal"> John pointed out that we already have JWT _claim_sources<o:p></o:p></p>
<p class="MsoNormal"> Tom said that the _claim_names are a dictionary<o:p></o:p></p>
<p class="MsoNormal"> DW pointed out that a JSON dictionary could have conflicts with JSON-LD claim renaming rules<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">SIOP Issues<o:p></o:p></p>
<p class="MsoNormal"> We ran out of time to get to this<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Open Issues<o:p></o:p></p>
<p class="MsoNormal"> <a href="https://bitbucket.org/openid/connect/issues?status=new&status=open">
https://bitbucket.org/openid/connect/issues?status=new&status=open</a><o:p></o:p></p>
<p class="MsoNormal"> We ran out of time to get to this<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Next Calls<o:p></o:p></p>
<p class="MsoNormal"> The next SIOP special call is Tuesday, April 13th at 3pm Pacific Time<o:p></o:p></p>
<p class="MsoNormal"> The next regular Connect call is on Monday, April 19th, 2021 at 4pm Pacific Time<o:p></o:p></p>
</div>
</body>
</html>