<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 14 (filtered medium)">
<style><!--
/* Font Definitions */
@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:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
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="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">Spec call notes 12-Oct-15<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">Edmund Jay<o:p></o:p></p>
<p class="MsoNormal">John Bradley<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Agenda<o:p></o:p></p>
<p class="MsoNormal"> Tokyo workshop after IETF 94 Yokohama<o:p></o:p></p>
<p class="MsoNormal"> Workshop before IIW<o:p></o:p></p>
<p class="MsoNormal"> Name of the HTTP-Based Logout spec<o:p></o:p></p>
<p class="MsoNormal"> Strong Authentication Working Group Proposal<o:p></o:p></p>
<p class="MsoNormal"> Certification<o:p></o:p></p>
<p class="MsoNormal"> [Openid-specs-ab] Attacking OpenID Connect 1.0 - Malicious Endpoints Attack<o:p></o:p></p>
<p class="MsoNormal"> Use of Session ID in HTTP-Based and Back-Channel logout specs<o:p></o:p></p>
<p class="MsoNormal"> Open Issues<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Tokyo workshop after IETF 94 Yokohama<o:p></o:p></p>
<p class="MsoNormal"> Presenters should send abstracts and bios to summit2015-info@openid.or.jp and Nat<o:p></o:p></p>
<p class="MsoNormal"> Mike will do a hands-on session to help people do certification<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Workshop before IIW<o:p></o:p></p>
<p class="MsoNormal"> Roland will do demos during the workshop<o:p></o:p></p>
<p class="MsoNormal"> During IIW we will try to help more people do certifications<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Name of the HTTP-Based Logout spec<o:p></o:p></p>
<p class="MsoNormal"> We will change the name to Front-Channel Logout, as proposed by Nov Matake<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Strong Authentication Working Group Proposal<o:p></o:p></p>
<p class="MsoNormal"> Scope of work is expected to include defining a few ACR values and eventually use of token binding<o:p></o:p></p>
<p class="MsoNormal"> Nat thinks this makes sense and is willing to be a proposer<o:p></o:p></p>
<p class="MsoNormal"> That leaves one more proposer needed<o:p></o:p></p>
<p class="MsoNormal"> We need to clarify that defining using proof-of-possession in ID Tokens is in scope in the charter<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Certification<o:p></o:p></p>
<p class="MsoNormal"> Edmund reported that Roland still needs to fix a few bugs for his RP tests to succeed<o:p></o:p></p>
<p class="MsoNormal"> Roland expects to do that tomorrow<o:p></o:p></p>
<p class="MsoNormal"> Deutsche Telekom, Microsoft, Roland Hedberg, and Cal Heldenbrand of RESO added new OP certifications<o:p></o:p></p>
<p class="MsoNormal"> See http://openid.net/certification/ and http://openid.net/2015/10/12/openid-connects-real-estate-identity/<o:p></o:p></p>
<p class="MsoNormal"> Verizon and Privo are also working on OP certifications<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">[Openid-specs-ab] Attacking OpenID Connect 1.0 - Malicious Endpoints Attack<o:p></o:p></p>
<p class="MsoNormal"> This is the subject of open issue #979<o:p></o:p></p>
<p class="MsoNormal"> We can spend time on this during IIW<o:p></o:p></p>
<p class="MsoNormal"> Mike pointed out in the multi-tenant case that you may not know the issuer until runtime<o:p></o:p></p>
<p class="MsoNormal"> But that you can match on the jwks_uri to verify that the issuer is legal<o:p></o:p></p>
<p class="MsoNormal"> We should probably have a general discussion on security issues for multi-tenant implementations<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Use of Session ID in HTTP-Based and Back-Channel logout specs<o:p></o:p></p>
<p class="MsoNormal"> In Front Channel, standalone identifier with enough entropy to uniquely identify a session<o:p></o:p></p>
<p class="MsoNormal"> In Back Channel, it identifies the User Agent or Device<o:p></o:p></p>
<p class="MsoNormal"> John - Maybe we should just call them different things<o:p></o:p></p>
<p class="MsoNormal"> John - The back channel one is more of a device/user agent identifier generated by the IdP<o:p></o:p></p>
<p class="MsoNormal"> John - You want the back channel device identifier to be user specific<o:p></o:p></p>
<p class="MsoNormal"> Nat - Maybe call it User Device Identifier ("udi")<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"> There are no new open issues<o:p></o:p></p>
</div>
</body>
</html>