<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;
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">
<div class="WordSection1">
<p class="MsoNormal">Spec call notes 20-Feb-17<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">John Bradley<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">Rich Levinson<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"> Mutual TLS OAuth Draft<o:p></o:p></p>
<p class="MsoNormal"> Certification Update<o:p></o:p></p>
<p class="MsoNormal"> OAuth Security Threats Information<o:p></o:p></p>
<p class="MsoNormal"> Open Issues<o:p></o:p></p>
<p class="MsoNormal"> Stephen Farrell's feedback on draft-ietf-oauth-jwsreq<o:p></o:p></p>
<p class="MsoNormal"> Next Call<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Mutual TLS OAuth Draft<o:p></o:p></p>
<p class="MsoNormal"> There is interest in draft-campbell-oauth-tls-client-auth-00 in the FAPI WG<o:p></o:p></p>
<p class="MsoNormal"> Some banking authorities mandate using certificates<o:p></o:p></p>
<p class="MsoNormal"> See https://www.nds.rub.de/media/ei/veroeffentlichungen/2017/01/30/oidc-security.pdf<o:p></o:p></p>
<p class="MsoNormal"> We will talk about this at IETF 98 in Chicago<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Certification Update<o:p></o:p></p>
<p class="MsoNormal"> RP Certification launched http://openid.net/2017/02/14/openid-connect-relying-party-certification-adoption/<o:p></o:p></p>
<p class="MsoNormal"> Certified Implementations are now listed at http://openid.net/developers/certified/<o:p></o:p></p>
<p class="MsoNormal"> We surveyed those who have certified on their experiences<o:p></o:p></p>
<p class="MsoNormal"> Lots of good feedback was received which Don and Mike will go through and publish<o:p></o:p></p>
<p class="MsoNormal"> Hans Zandbelt has been working with Roland on information transfer and documentation<o:p></o:p></p>
<p class="MsoNormal"> Additional profiles need to be defined and reviewed by the working group<o:p></o:p></p>
<p class="MsoNormal"> Such as form post response mode<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">OAuth Security Threats Information<o:p></o:p></p>
<p class="MsoNormal"> Nat said that the University of Trier researchers are publishing their full paper in April<o:p></o:p></p>
<p class="MsoNormal"> They provided feedback on the tests, some of which was incorporated into the tests<o:p></o:p></p>
<p class="MsoNormal"> We don't have OAuth Mix-Up tests in the certification suite at present<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"> #1009: Contradictory statements about ID Token azp Claim<o:p></o:p></p>
<p class="MsoNormal"> Much of this ground has already been covered in issue #973<o:p></o:p></p>
<p class="MsoNormal"> We propose to address it when addressing #973<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Stephen Farrell's feedback on draft-ietf-oauth-jwsreq<o:p></o:p></p>
<p class="MsoNormal"> Stephen is worried about parameters being able to be in two places and sometimes signed and sometimes not<o:p></o:p></p>
<p class="MsoNormal"> People are encourage to comment on the OAuth thread<o:p></o:p></p>
<p class="MsoNormal"> Being more strict wouldn't break connect OPs<o:p></o:p></p>
<p class="MsoNormal"> It would break the (very few) RPs that use this in mixed mode<o:p></o:p></p>
<p class="MsoNormal"> It's probably reasonable to tighten this up in the OAuth spec<o:p></o:p></p>
<p class="MsoNormal"> jwsreq needs an "updates" clause about 6749<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"> The next call is scheduled for Thursday, March 2nd at 7am Pacific Time<o:p></o:p></p>
</div>
</body>
</html>