<div dir="ltr">Hi Tom,<div><br></div><div>In conventional OpenID Connect (the model that is most widely used and deployed today), its assumed that the OpenID Provider is an HTTP based Authorization server (due the foundation of OAuth2.0). The self issued chapter however contemplates the question, what if the provider is instead an application running on the end users device such as a native app or PWA? This point is designed to address the issues associated with doing just that.<br clear="all"><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><br></div><div dir="ltr">Thanks,<br><table width="auto" cellpadding="0" cellspacing="0" border="0" style="color:rgb(0,0,0);font-family:Times;font-size:medium;border:0px"><tbody><tr style="font-family:"Helvetica Neue",Helvetica,Arial,sans-serif;font-size:11px;line-height:16px"><td width="125" valign="top"><a href="https://mattr.global" style="border:none;color:rgb(15,173,225)" target="_blank"><img src="https://mattr.global/assets/images/MattrLogo.png" alt="Mattr website" width="125" height="125" style="height:auto"></a></td><td width="16"> </td><td width="159" valign="top" style="color:rgb(51,49,50);font-size:12px"><table cellpadding="0" cellspacing="0" border="0" style="border:0px"><tbody><tr style="font-family:"Helvetica Neue",Helvetica,Arial,sans-serif;font-size:11px;line-height:16px"><td><strong style="font-size:12px">Tobias Looker</strong><br></td></tr><tr style="font-family:"Helvetica Neue",Helvetica,Arial,sans-serif;font-size:11px;line-height:16px"><td style="line-height:16px">Mattr</td></tr><tr style="font-family:"Helvetica Neue",Helvetica,Arial,sans-serif;font-size:11px;line-height:16px"><td style="line-height:16px;padding-top:12px">+64 (0) 27 378 0461<br><a href="mailto:tobias.looker@mattr.global" style="border:none;color:rgb(51,49,50)" target="_blank">tobias.looker@mattr.global</a></td></tr><tr style="font-family:"Helvetica Neue",Helvetica,Arial,sans-serif;font-size:11px;line-height:16px"><td style="font-size:12px;padding-top:12px"><table cellpadding="0" cellspacing="0" border="0" style="border:0px"><tbody><tr style="font-family:"Helvetica Neue",Helvetica,Arial,sans-serif;font-size:11px;line-height:16px"><td width="40"><a href="https://mattr.global" style="border:none;color:rgb(51,49,50);margin-right:12px" target="_blank"><img src="https://mattr.global/assets/images/website.png" alt="Mattr website" width="24" style="border:0px;height:40px;width:24px"></a></td><td width="40"><a href="https://www.linkedin.com/company/mattrglobal" style="border:none;color:rgb(51,49,50);margin-right:12px" target="_blank"><img src="https://mattr.global/assets/images/linkedin.png" alt="Mattr on LinkedIn" width="24" style="border:0px;height:40px;width:24px"></a></td><td width="40"><a href="https://twitter.com/mattrglobal" style="border:none;color:rgb(51,49,50);margin-right:12px" target="_blank"><img src="https://mattr.global/assets/images/twitter.png" alt="Mattr on Twitter" width="24" style="border:0px;height:40px;width:24px"></a></td><td width="40"><a href="https://github.com/mattrglobal" style="border:none;color:rgb(51,49,50);margin-right:12px" target="_blank"><img src="https://mattr.global/assets/images/github.png" alt="Mattr on Github" width="24" style="border:0px;height:40px;width:24px"></a></td></tr></tbody></table></td></tr></tbody></table></td></tr></tbody></table><br style="color:rgb(0,0,0);font-family:Times;font-size:medium"><small style="color:rgb(118,118,118);font-family:"Helvetica Neue",Helvetica,Arial,sans-serif;font-size:8px;line-height:14px">This communication, including any attachments, is confidential. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002.</small><br></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Dec 3, 2020 at 1:35 PM Tom Jones 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">not sure i understand the point of 3 - RP-OP colocation - pls provide a use case<br clear="all"><div><div><div dir="ltr"><div dir="ltr"><div>Peace ..tom</div></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Dec 2, 2020 at 4:00 PM Tobias Looker 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 class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hi All,<div><br></div><div>Over the past while, there has been a lot of interest and work going into a revision to chapter 7 of the OpenID Connect Core chapter (Self Issued Provider). It is my impression that because this chapter originally aimed to solve several quite large problems, we would benefit from classifying these better to ensure we can have the most productive conversations possible. My proposal, that I have already informally raised on the Pacific AB WG call, is to break apart the scope of SIOP into 5 separate problems.</div><div><br></div><div>1. Enabling portable subject identifiers between providers - Define how to use techniques such as asymmetric cryptography and higher level technologies like Decentralized Identifiers to create subject identifiers that are not intrinsically bound to a particular OP and hence can be ported between providers.<br></div><div>2. Solving for provider discovery and registration - Evaluating solutions to problems like the nascar problem, how does an RP come to have a relationship with an OP or understand its capabilities along with what role the user plays in this selection/discovery process.</div><div>3. RP - OP co-location on the same device - Dealing with the unique requirements that are brought about when the OP the RP is communicating with is on the same device (e.g in the form of a PWA or Native App), rather than a traditional Authorization server.</div><div>4. Credential Issuance support - Issuing credentials from OpenID Connect flows.</div><div>5. Credential Presentation support - Presenting credentials in OpenID Connect flows.</div><div><br></div><div>Its important to note that in my opinion only problems 1,2 and 3 were in the original scope of the SIOP chapter however due to the continued evolution of the SSI/Decentralized Identity and Verifiable Credential space, many uses cases that SIOP has come to be associated with involve verifiable credentials and there for problems 4. and 5. should be addressed.<div><div dir="ltr"><div dir="ltr"><br></div><div dir="ltr">Thanks,<br><table style="color:rgb(0,0,0);font-family:Times;font-size:medium;border:0px none" width="auto" cellspacing="0" cellpadding="0" border="0"><tbody><tr style="font-family:"Helvetica Neue",Helvetica,Arial,sans-serif;font-size:11px;line-height:16px"><td width="125" valign="top"><a href="https://mattr.global" style="border:medium none;color:rgb(15,173,225)" target="_blank"><img src="https://mattr.global/assets/images/MattrLogo.png" alt="Mattr website" style="height: auto;" width="125" height="125"></a></td><td width="16"> </td><td style="color:rgb(51,49,50);font-size:12px" width="159" valign="top"><table style="border:0px none" cellspacing="0" cellpadding="0" border="0"><tbody><tr style="font-family:"Helvetica Neue",Helvetica,Arial,sans-serif;font-size:11px;line-height:16px"><td><strong style="font-size:12px">Tobias Looker</strong><br></td></tr><tr style="font-family:"Helvetica Neue",Helvetica,Arial,sans-serif;font-size:11px;line-height:16px"><td style="line-height:16px">Mattr</td></tr><tr style="font-family:"Helvetica Neue",Helvetica,Arial,sans-serif;font-size:11px;line-height:16px"><td style="line-height:16px;padding-top:12px">+64 (0) 27 378 0461<br><a href="mailto:tobias.looker@mattr.global" style="border:medium none;color:rgb(51,49,50)" target="_blank">tobias.looker@mattr.global</a></td></tr><tr style="font-family:"Helvetica Neue",Helvetica,Arial,sans-serif;font-size:11px;line-height:16px"><td style="font-size:12px;padding-top:12px"><table style="border:0px none" cellspacing="0" cellpadding="0" border="0"><tbody><tr style="font-family:"Helvetica Neue",Helvetica,Arial,sans-serif;font-size:11px;line-height:16px"><td width="40"><a href="https://mattr.global" style="border:medium none;color:rgb(51,49,50);margin-right:12px" target="_blank"><img src="https://mattr.global/assets/images/website.png" alt="Mattr website" style="border: 0px none; height: 40px; width: 24px;" width="24"></a></td><td width="40"><a href="https://www.linkedin.com/company/mattrglobal" style="border:medium none;color:rgb(51,49,50);margin-right:12px" target="_blank"><img src="https://mattr.global/assets/images/linkedin.png" alt="Mattr on LinkedIn" style="border: 0px none; height: 40px; width: 24px;" width="24"></a></td><td width="40"><a href="https://twitter.com/mattrglobal" style="border:medium none;color:rgb(51,49,50);margin-right:12px" target="_blank"><img src="https://mattr.global/assets/images/twitter.png" alt="Mattr on Twitter" style="border: 0px none; height: 40px; width: 24px;" width="24"></a></td><td width="40"><a href="https://github.com/mattrglobal" style="border:medium none;color:rgb(51,49,50);margin-right:12px" target="_blank"><img src="https://mattr.global/assets/images/github.png" alt="Mattr on Github" style="border: 0px none; height: 40px; width: 24px;" width="24"></a></td></tr></tbody></table></td></tr></tbody></table></td></tr></tbody></table><br style="color:rgb(0,0,0);font-family:Times;font-size:medium"><small style="color:rgb(118,118,118);font-family:"Helvetica Neue",Helvetica,Arial,sans-serif;font-size:8px;line-height:14px">This communication, including any attachments, is confidential. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002.</small><br></div></div></div></div></div>
<br>
<pre style="font-family:"Courier New",Courier,monospace,arial,sans-serif;margin-top:0px;margin-bottom:0px;white-space:pre-wrap;background-color:rgb(255,255,255);font-size:14px">This communication, including any attachments, is confidential. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002.</pre>_______________________________________________<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>
_______________________________________________<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>
<br>
<pre style="font-family:"Courier New",Courier,monospace,arial,sans-serif;margin-top:0px;margin-bottom:0px;white-space:pre-wrap;background-color:rgb(255,255,255);font-size:14px">This communication, including any attachments, is confidential. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002.</pre>