<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;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
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">
<div class="WordSection1">
<p class="MsoNormal">Spec Call Notes 11-Apr-19<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">Nat Sakimura<o:p></o:p></p>
<p class="MsoNormal">George Fletcher<o:p></o:p></p>
<p class="MsoNormal">Brian Campbell<o:p></o:p></p>
<p class="MsoNormal">John Bradley<o:p></o:p></p>
<p class="MsoNormal">Rich Levinson<o:p></o:p></p>
<p class="MsoNormal">Bjorn Hjelm<o:p></o:p></p>
<p class="MsoNormal">Torsten Lodderstedt<o:p></o:p></p>
<p class="MsoNormal">Tom Jones<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">OAuth JAR<o:p></o:p></p>
<p class="MsoNormal"> Nat asked for feedback on the OAuth JAR spec from John<o:p></o:p></p>
<p class="MsoNormal"> John is working on addressing feedback received during the OAuth Security Workshop<o:p></o:p></p>
<p class="MsoNormal"> It's already gone through the IESG telechat already so the authors are looking to minimize the changes made<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">authentication_failed Error Code Draft<o:p></o:p></p>
<p class="MsoNormal"> No comments were received during the adoption comment period, so the draft is adopted<o:p></o:p></p>
<p class="MsoNormal"> The working group requested to change the name to unmet_authentication_requirements on the 1-Apr-19 call<o:p></o:p></p>
<p class="MsoNormal"> Torsten will update the error code name and we'll publish a working group draft<o:p></o:p></p>
<p class="MsoNormal"> This addresses issue https://bitbucket.org/openid/connect/issues/1029/authentication_failed-error-response<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">OpenID Connect for Identity Proofing<o:p></o:p></p>
<p class="MsoNormal"> A working group draft was published at https://openid.net/specs/openid-connect-4-identity-assurance.html<o:p></o:p></p>
<p class="MsoNormal"> Torsten has received some private feedback<o:p></o:p></p>
<p class="MsoNormal"> More working group feedback is solicited<o:p></o:p></p>
<p class="MsoNormal"> Bjorn and Daniel Fett will propose a session at IIW about the draft<o:p></o:p></p>
<p class="MsoNormal"> Mike agreed to help facilitate the session<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">OpenID Certification<o:p></o:p></p>
<p class="MsoNormal"> Roland Hedberg continues refining the initial logout certification tests<o:p></o:p></p>
<p class="MsoNormal"> Filip Skokan has been super-helpful in doing early tests of the tests<o:p></o:p></p>
<p class="MsoNormal"> Hans has also helped get them ready for people to run<o:p></o:p></p>
<p class="MsoNormal"> They are deployed at https://new-op.certification.openid.net:60000/ and https://new-rp.certification.openid.net:8080/<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> Expect an announcement requesting that people test the tests shortly<o:p></o:p></p>
<p class="MsoNormal"> Third Party-Initiated Login tests have been available to test since February<o:p></o:p></p>
<p class="MsoNormal"> Thus far, we're not aware that they have been tested<o:p></o:p></p>
<p class="MsoNormal"> We observed on the call that IdP-initiated login is much more common in the SAML world than the Connect world<o:p></o:p></p>
<p class="MsoNormal"> Mike will send a reminder to the working group of the availability of the tests<o:p></o:p></p>
<p class="MsoNormal"> FAPI certification launched on April 1st<o:p></o:p></p>
<p class="MsoNormal"> See the completed FAPI certifications at https://openid.net/certification/#FAPI_OPs<o:p></o:p></p>
<p class="MsoNormal"> The Connect certification pricing will go up on June 1st<o:p></o:p></p>
<p class="MsoNormal"> See https://openid.net/2019/02/21/openid-certification-program-expansion-and-fee-update/<o:p></o:p></p>
<p class="MsoNormal"> Those considering new certifications will get a price break by doing so in April or May<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"> https://bitbucket.org/openid/connect/issues?status=new&status=open<o:p></o:p></p>
<p class="MsoNormal"> #1067 Add Privacy Considerations<o:p></o:p></p>
<p class="MsoNormal"> Torsten will do this<o:p></o:p></p>
<p class="MsoNormal"> #1068 Follow ISO Rules<o:p></o:p></p>
<p class="MsoNormal"> This is a tracking issue. We will review the document in this regard in the future.<o:p></o:p></p>
<p class="MsoNormal"> #1069 Identity Assurance Section 5.1 on reason for request<o:p></o:p></p>
<p class="MsoNormal"> This had been heavily discussed in the comment and on list<o:p></o:p></p>
<p class="MsoNormal"> Mike had made the point that it's always up to the two parties what information to exchange<o:p></o:p></p>
<p class="MsoNormal"> We shouldn't start mandating specific information now<o:p></o:p></p>
<p class="MsoNormal"> Tom said that maybe we could reference legal agreements in machine-processable fashion<o:p></o:p></p>
<p class="MsoNormal"> George said that that would be a whole different standardization effort<o:p></o:p></p>
<p class="MsoNormal"> George said that in some cases, the OP already knows that there is consent<o:p></o:p></p>
<p class="MsoNormal"> Torsten said that the OP always needs to understand the legal basis for sharing information with the RP<o:p></o:p></p>
<p class="MsoNormal"> Tom said that there are different legal jurisdictions<o:p></o:p></p>
<p class="MsoNormal"> George said that legal information can be exchanged offline and need not be part of the protocol<o:p></o:p></p>
<p class="MsoNormal"> George reminded us that we already have a prompt=consent parameter<o:p></o:p></p>
<p class="MsoNormal"> We commented in the issue that a concrete proposal is needed<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Next Call<o:p></o:p></p>
<p class="MsoNormal"> Monday, April 15 at 4pm Pacific Time<o:p></o:p></p>
</div>
</body>
</html>