<div dir="ltr">that makes no sense to me.<div>I guess you are saying that no one can read any part of an id token without first evaluating all of the encoded stuff first?</div><div>I really do not like the thought of that.</div><div>It seems to violate the whole idea of the element tags.</div><div><br clear="all"><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><span style="background-color:rgb(242,242,242);color:rgba(0,0,0,0.9);font-family:-apple-system,system-ui,system-ui,"Segoe UI",Roboto,"Helvetica Neue","Fira Sans",Ubuntu,Oxygen,"Oxygen Sans",Cantarell,"Droid Sans","Apple Color Emoji","Segoe UI Emoji","Segoe UI Symbol","Lucida Grande",Helvetica,Arial,sans-serif;font-size:14px;white-space:pre-wrap">Be the change you want to see in the world </span>..tom</div></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Apr 7, 2021 at 6:53 PM Kristina Yasuda via Openid-specs-ab <<a href="mailto:openid-specs-ab@lists.openid.net">openid-specs-ab@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 dir="ltr">
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<span style="color:rgb(0,0,0);font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt">VC specification defined `vp`, `vc` claims, but they are defined only to include "tthose parts of the standard verifiable credentials and verifiable presentations
where no explicit encoding rules for JWT exist". Hence </span><span style="color:rgb(0,0,0);font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt">`vp`, `vc` claims are only a part of the the entire VP, VC. </span><br>
</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<span style="background-color:rgb(255,255,255);display:inline"><br>
</span></div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<span style="background-color:rgb(255,255,255);display:inline">There is a need a define a standard way to return VPs using OpenID Connect, and the proposal is to use `vp_jwt`, `vp_ldp`
<span style="background-color:rgb(255,255,255);display:inline">claims<span> </span></span>that would include entire VP inside the ID token. (VP in a JWT format inside `<span style="background-color:rgb(255,255,255);display:inline">vp_jwt`</span> would
include `vp` claim) </span></div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<span style="background-color:rgb(255,255,255);display:inline"><span style="margin:0px;font-size:12pt">Example can be found here: <a href="https://hackmd.io/grbDXDHqTE6lhu6fvVFIuA" id="gmail-m_-6803738454427501971LPlnk110968" target="_blank">Examples for the vp_jwt, vp_ldp proposal - HackMD</a></span><br>
</span></div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
Note that this proposal is intended to work not only with SIOP V2, but also if VPs are to be returned from the user_info endpoint for example.</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<span style="background-color:rgb(255,255,255);display:inline"><br>
</span></div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<span style="background-color:rgb(255,255,255);display:inline">Best,</span></div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<span style="background-color:rgb(255,255,255);display:inline">Kristina</span></div>
<div id="gmail-m_-6803738454427501971appendonsend"></div>
<hr style="display:inline-block;width:98%">
<div id="gmail-m_-6803738454427501971divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>差出人:</b> Openid-specs-ab <<a href="mailto:openid-specs-ab-bounces@lists.openid.net" target="_blank">openid-specs-ab-bounces@lists.openid.net</a>> が ANTHONY NADALIN via Openid-specs-ab <<a href="mailto:openid-specs-ab@lists.openid.net" target="_blank">openid-specs-ab@lists.openid.net</a>> の代理で送信<br>
<b>送信日時:</b> 2021年4月8日 10:09<br>
<b>宛先:</b> Artifact Binding/Connect Working Group <<a href="mailto:openid-specs-ab@lists.openid.net" target="_blank">openid-specs-ab@lists.openid.net</a>><br>
<b>CC:</b> Anthony Nadalin <<a href="mailto:nadalin@prodigy.net" target="_blank">nadalin@prodigy.net</a>>; <a href="mailto:oliver.terbu@mesh.xyz" target="_blank">oliver.terbu@mesh.xyz</a> <<a href="mailto:oliver.terbu@mesh.xyz" target="_blank">oliver.terbu@mesh.xyz</a>><br>
<b>件名:</b> Re: [Openid-specs-ab] Defining JWT Claims to represent W3C Verifiable Credentials objects</font>
<div> </div>
</div>
<div>
<div dir="auto" style="direction:ltr;margin:0px;padding:0px;font-family:sans-serif;font-size:11pt;color:black">
I don't quite understand this proposal as if you read the verifiable credential specification you will see a section called JWT encoding and JWT decoding based upon what Mike is written I don't understand how you could abide by a fully compliant verifiable
credential specification without encoding and decoding JWT's into verifiable credentials.<br>
</div>
<div dir="auto" style="direction:ltr;margin:0px;padding:0px;font-family:sans-serif;font-size:11pt;color:black">
<br>
</div>
<div dir="auto" style="direction:ltr;margin:0px;padding:0px;font-family:sans-serif;font-size:11pt;color:black">
<span id="gmail-m_-6803738454427501971x_OutlookSignature">
<div dir="auto" style="direction:ltr;margin:0px;padding:0px;font-family:sans-serif;font-size:11pt;color:black">
Get <a href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Faka.ms%2FAAb9ysg&data=04%7C01%7CKristina.Yasuda%40microsoft.com%7C692e57f56b6a438a91ab08d8fa2d9bad%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637534421379557988%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=FnWyXWRCNoPtQ%2FoIYYiXJKqx%2BPdJwGjmPDNEm%2BgyZ3I%3D&reserved=0" target="_blank">
Outlook for Android</a></div>
</span><br>
</div>
<hr style="display:inline-block;width:98%">
<div id="gmail-m_-6803738454427501971x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> Openid-specs-ab <<a href="mailto:openid-specs-ab-bounces@lists.openid.net" target="_blank">openid-specs-ab-bounces@lists.openid.net</a>> on behalf of Tom Jones via Openid-specs-ab <<a href="mailto:openid-specs-ab@lists.openid.net" target="_blank">openid-specs-ab@lists.openid.net</a>><br>
<b>Sent:</b> Wednesday, April 7, 2021 6:00:29 PM<br>
<b>To:</b> Artifact Binding/Connect Working Group <<a href="mailto:openid-specs-ab@lists.openid.net" target="_blank">openid-specs-ab@lists.openid.net</a>><br>
<b>Cc:</b> Tom Jones <<a href="mailto:thomasclinganjones@gmail.com" target="_blank">thomasclinganjones@gmail.com</a>>; <a href="mailto:oliver.terbu@mesh.xyz" target="_blank">oliver.terbu@mesh.xyz</a> <<a href="mailto:oliver.terbu@mesh.xyz" target="_blank">oliver.terbu@mesh.xyz</a>><br>
<b>Subject:</b> Re: [Openid-specs-ab] Defining JWT Claims to represent W3C Verifiable Credentials objects</font>
<div> </div>
</div>
<div>
<div dir="ltr">I have an alternate proposal. In my system the claim should have a name that represents what it is. For example the existing claims acr and amr should be enabled to carry a vc or vp as its value. In this system the encoding of the value would
carry the syntax of the claim, beit vc-sjon, vc-ld or whatever. The one proposal I did make was to use jose encoding. If we wanted to use this the jose header could contain the syntax of the contained element as Mike has indicated in his proposal.
<div><br>
</div>
<div>I think it is not helpful for the name of the claim to be just the syntax of the element.</div>
<div><br clear="all">
<div>
<div dir="ltr">
<div dir="ltr">
<div><span style="background-color:rgb(242,242,242);color:rgba(0,0,0,0.9);font-size:14px;white-space:pre-wrap">Be the change you want to see in the world
</span>..tom</div>
</div>
</div>
</div>
<br>
</div>
</div>
<br>
<div>
<div dir="ltr">On Wed, Apr 7, 2021 at 5:25 PM Mike Jones via Openid-specs-ab <<a href="mailto:openid-specs-ab@lists.openid.net" target="_blank">openid-specs-ab@lists.openid.net</a>> wrote:<br>
</div>
<blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div lang="EN-US">
<div>
<p>In our discussions over the past few months, it’s become clear that there are multiple use cases where different forms of W3C Verifiable Credential objects will be communicated as JWT claims (or as UserInfo Endpoint claims). I had
a useful conversation with Oliver Terbu and Kristina Yasuda this week during which we agreed that it would be useful to write a short, focused specification defining and registering JWT claims enabling standard representations for this purpose. These claims
could be used both by SIOP use cases and other use cases.<u></u><u></u></p>
<p><u></u> <u></u></p>
<p>Bear in mind that the W3C Verifiable Credentials specification defines two representations of the objects that it defines – JWT and JSON-LD and it also orthogonally defines two kinds of objects – Verifiable Credentials and Verifiable
Presentations. Thus, there are actually four different data types that these use cases might want to utilize.<u></u><u></u></p>
<p><u></u> <u></u></p>
<p>I would therefore propose the following four claim definitions for these purposes:<u></u><u></u></p>
<p><u></u> <u></u></p>
<ul type="disc" style="margin-top:0in">
<li style="margin-left:0in">
<b><span style="font-family:"Courier New"">vc_jwt</span></b>: A claim whose value is a W3C Verifiable Credential object using the JWT representation, which is a JSON string. The claim’s value may also be an array of W3C Verifiable Credential objects using
the JWT representation if the use case calls for multiple JWT VCs.<u></u><u></u></li><li style="margin-left:0in">
<b><span style="font-family:"Courier New"">vp_jwt</span></b>: A claim whose value is a W3C Verifiable Presentation object using the JWT representation, which is a JSON string. The claim’s value may also be an array of W3C Verifiable Presentation objects using
the JWT representation if the use case calls for multiple JWT VPs.<u></u><u></u></li><li style="margin-left:0in">
<b><span style="font-family:"Courier New"">vc_ld</span></b>: A claim whose value is a W3C Verifiable Credential object using the JSON-LD representation, which is a JSON object. The claim’s value may also be an array of W3C Verifiable Credential objects using
the JSON-LD representation if the use case calls for multiple JSON-LD VCs.<u></u><u></u></li><li style="margin-left:0in">
<b><span style="font-family:"Courier New"">vp_ld</span></b>: A claim whose value is a W3C Verifiable Presentation object using the JSON-LD representation, which is a JSON object. The claim’s value may also be an array of W3C Verifiable Presentation objects
using the JSON-LD representation if the use case calls for multiple JSON-LD VPs.<u></u><u></u></li></ul>
<p><u></u> <u></u></p>
<p>Let’s discuss this proposal during the European-friendly Connect call ~13.5 hours from now.<u></u><u></u></p>
<p><u></u> <u></u></p>
<p> -- Mike<u></u><u></u></p>
<p><u></u> <u></u></p>
</div>
</div>
_______________________________________________<br>
Openid-specs-ab mailing list<br>
<a href="mailto:Openid-specs-ab@lists.openid.net" target="_blank">Openid-specs-ab@lists.openid.net</a><br>
<a href="https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.openid.net%2Fmailman%2Flistinfo%2Fopenid-specs-ab&data=04%7C01%7CKristina.Yasuda%40microsoft.com%7C692e57f56b6a438a91ab08d8fa2d9bad%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637534421379557988%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=t%2Bg7TOqpJ6MugoogevZ2ga8oCZuxQCVPf5e2GajhTAA%3D&reserved=0" rel="noreferrer" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs-ab</a><br>
</blockquote>
</div>
</div>
</div>
</div>
_______________________________________________<br>
Openid-specs-ab mailing list<br>
<a href="mailto:Openid-specs-ab@lists.openid.net" target="_blank">Openid-specs-ab@lists.openid.net</a><br>
<a href="http://lists.openid.net/mailman/listinfo/openid-specs-ab" rel="noreferrer" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs-ab</a><br>
</blockquote></div>