<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 24-Jan-13<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">Justin Richer<o:p></o:p></p>
<p class="MsoNormal">Roland Hedberg<o:p></o:p></p>
<p class="MsoNormal">Pamela Dingle<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"><o:p> </o:p></p>
<p class="MsoNormal">Agenda:<o:p></o:p></p>
<p class="MsoNormal"> Open Issues<o:p></o:p></p>
<p class="MsoNormal"> Implementer's Drafts Work Status<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 were no new open issues<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Implementer's Drafts Work Status:<o:p></o:p></p>
<p class="MsoNormal"> Mike released release candidate versions yesterday<o:p></o:p></p>
<p class="MsoNormal"> We will give people through Monday to review them<o:p></o:p></p>
<p class="MsoNormal"> We will decide on the Monday call whether we're ready to release the Implementer's Draft versions<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Implementation Status:<o:p></o:p></p>
<p class="MsoNormal"> We want to get interop on WebFinger-based discovery before releasing the Implementer's Drafts<o:p></o:p></p>
<p class="MsoNormal"> Roland has code<o:p></o:p></p>
<p class="MsoNormal"> Edmund has code<o:p></o:p></p>
<p class="MsoNormal"> Both need to make it the default<o:p></o:p></p>
<p class="MsoNormal"> Justin has server side code<o:p></o:p></p>
<p class="MsoNormal"> Anomalies noticed by Pam while working on the native client application:<o:p></o:p></p>
<p class="MsoNormal"> Edmund's implementation has an "ops" claim<o:p></o:p></p>
<p class="MsoNormal"> Not everyone has a "jti" claim<o:p></o:p></p>
<p class="MsoNormal"> Not everyone has "sub" yet - for instance, Ping<o:p></o:p></p>
<p class="MsoNormal"> Ping's implementation still has to make several updates, including "sub", JWK name changes, etc.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> The most important change is to switch discovery to WebFinger<o:p></o:p></p>
<p class="MsoNormal"> We'd like to get WebFinger interop before the implementer's draft release<o:p></o:p></p>
<p class="MsoNormal"> Also, there were registration parameter name changes<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> Implementers should please post to the interop list as changes are pushed live<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Pam's Comments on Basic:<o:p></o:p></p>
<p class="MsoNormal"> Basic 2.2.1. Client Prepares Authorization Request says<o:p></o:p></p>
<p class="MsoNormal"> Clients MAY construct the request using the HTTP GET or the HTTP POST method as defined in RFC 2616 [RFC2616].<o:p></o:p></p>
<p class="MsoNormal"> Standard 2.3 says<o:p></o:p></p>
<p class="MsoNormal"> Authorization Servers MUST support the use of the HTTP "GET" and "POST" methods defined in RFC 2616 [RFC2616] at the Authorization Endpoint.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> We don't need to express a preference between the methods in Basic<o:p></o:p></p>
<p class="MsoNormal"> We may say that they can use either because OPs must support both<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> Basic 2.2.6. Client Obtains ID Token and Access Token<o:p></o:p></p>
<p class="MsoNormal"> Basic 2.2.6.1 says no preference between POST or GET<o:p></o:p></p>
<p class="MsoNormal"> References 4.1.3. Access Token Request of OAuth 2.0 [RFC6749]<o:p></o:p></p>
<p class="MsoNormal"> References 3.2.1. Client Authentication<o:p></o:p></p>
<p class="MsoNormal"> References 2.3.1. Client Password<o:p></o:p></p>
<p class="MsoNormal"> Recommends using Basic in authorization header<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> We should recommend putting the client credentials in the Authorization header in Basic<o:p></o:p></p>
<p class="MsoNormal"> As recommended in OAuth 2.3.1<o:p></o:p></p>
<p class="MsoNormal"> We may also want to mention that this is the client_secret_basic method from Registration<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> OAuth 3.2. Token Endpoint says<o:p></o:p></p>
<p class="MsoNormal"> The client MUST use the HTTP "POST" method when making access token requests.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> The phrase "Access Token Request" should appear in 2.2.6<o:p></o:p></p>
<p class="MsoNormal"> We might also want the term "Client Authentication" to appear in 2.2.6.1<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> We may need to clarify what we mean by "Token Endpoint" - "OAuth Access Token Endpoint"<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Native client:<o:p></o:p></p>
<p class="MsoNormal"> Pam has credentials for Oreo, Edmund's, Ping's, and is trying with AOL<o:p></o:p></p>
<p class="MsoNormal"> She is planning to also do Mitre, but it needs to be hosted<o:p></o:p></p>
<p class="MsoNormal"> Pam believes she is one bug from doing a release of the Native Client<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Key Rollover:<o:p></o:p></p>
<p class="MsoNormal"> This is still an open problem, per discussions on the list<o:p></o:p></p>
<p class="MsoNormal"> John still needs to write up possibilities<o:p></o:p></p>
<p class="MsoNormal"> We may want to add "exp" (expiration time) to JWK<o:p></o:p></p>
<p class="MsoNormal"> Breno also made comments about how rollover is harder for encryption keys<o:p></o:p></p>
<p class="MsoNormal"> We agreed that this is important address for the sake of long-term usability of the protocol<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Held Issues:<o:p></o:p></p>
<p class="MsoNormal"> We reviewed all the held issues<o:p></o:p></p>
<p class="MsoNormal"> Many were closed as no longer relevant - most being about the former Session Management spec<o:p></o:p></p>
<p class="MsoNormal"> #364 was reopened: Term "Session" not defined<o:p></o:p></p>
<p class="MsoNormal"> A task to register the /.well-known/openid-configuration URI with IANA was also reinstated<o:p></o:p></p>
<p class="MsoNormal"> We agreed that we should make all registration requests once the Implementer's Drafts are published<o:p></o:p></p>
</div>
</body>
</html>