<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;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 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;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@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"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Mike Jones
<br>
<b>Sent:</b> Monday, October 21, 2013 4:11 PM<br>
<b>To:</b> Edmund Jay; Tom Brown; Johann Nallathamby; Brian Campbell; Pamela Dingle; John Ehrig; Jack Greenberg; Morteza Ansari; Lucy Lynch; Justin P. Richer; Breno de Medeiros; Tim Bray; John Bradley; Morten V. Christiansen; Henrik Biering; Naveen Agarwal;
George Fletcher; Blake Brannon; Michael Engan; Ashish Jain; Adam Dawes<br>
<b>Subject:</b> OpenID Connect Face-to-Face Meeting 21-Oct-13<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">OpenID Connect Face-to-Face Meeting 21-Oct-13<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Attendees:<o:p></o:p></p>
<p class="MsoNormal"> Mike Jones<o:p></o:p></p>
<p class="MsoNormal"> Edmund Jay<o:p></o:p></p>
<p class="MsoNormal"> Tom Brown<o:p></o:p></p>
<p class="MsoNormal"> Johann Nallathamby<o:p></o:p></p>
<p class="MsoNormal"> Brian Campbell<o:p></o:p></p>
<p class="MsoNormal"> Pam Dingle<o:p></o:p></p>
<p class="MsoNormal"> John Ehrig<o:p></o:p></p>
<p class="MsoNormal"> Jack Greenberg<o:p></o:p></p>
<p class="MsoNormal"> Morteza Ansari<o:p></o:p></p>
<p class="MsoNormal"> Lucy Lynch<o:p></o:p></p>
<p class="MsoNormal"> Justin Richer<o:p></o:p></p>
<p class="MsoNormal"> Breno de Medeiros<o:p></o:p></p>
<p class="MsoNormal"> Tim Bray<o:p></o:p></p>
<p class="MsoNormal"> John Bradley<o:p></o:p></p>
<p class="MsoNormal"> Morten V. Christiansen<o:p></o:p></p>
<p class="MsoNormal"> Henrik Biering<o:p></o:p></p>
<p class="MsoNormal"> Naveen Agarwal<o:p></o:p></p>
<p class="MsoNormal"> George Fletcher<o:p></o:p></p>
<p class="MsoNormal"> Blake Brannon<o:p></o:p></p>
<p class="MsoNormal"> Michael Engan<o:p></o:p></p>
<p class="MsoNormal"> Ashish Jain<o:p></o:p></p>
<p class="MsoNormal"> Adam Dawes<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"> Structure of Authentication Section<o:p></o:p></p>
<p class="MsoNormal"> Review of <a href="http://openid.net/specs/openid-connect-core-1_0.html#HybridIDToken2">
http://openid.net/specs/openid-connect-core-1_0.html#HybridIDToken2</a><o:p></o:p></p>
<p class="MsoNormal"> Review of <a href="http://openid.net/specs/openid-connect-core-1_0.html#HybridAccessToken2">
http://openid.net/specs/openid-connect-core-1_0.html#HybridAccessToken2</a><o:p></o:p></p>
<p class="MsoNormal"> Why do we require POST support at the Authorization Endpoint?<o:p></o:p></p>
<p class="MsoNormal"> Why are we allowing http redirect_uri values when apparently OAuth doesn’t?<o:p></o:p></p>
<p class="MsoNormal"> Why is the id_token_hint recommended for prompt=none?<o:p></o:p></p>
<p class="MsoNormal"> "The Authorization Code Flow is suitable for Clients that can securely maintain a Client Secret..."<o:p></o:p></p>
<p class="MsoNormal"> Where should the Client Authentication text be?<o:p></o:p></p>
<p class="MsoNormal"> Should the "iss", "aud", "redirect_uri", etc. contain a trailing slash?<o:p></o:p></p>
<p class="MsoNormal"> Discussion of redirect_uri matching<o:p></o:p></p>
<p class="MsoNormal"> How should the HTTP Form Post text be structured?<o:p></o:p></p>
<p class="MsoNormal"> Which specs do we make Final and which do we make Implementer's Drafts?<o:p></o:p></p>
<p class="MsoNormal"> Next steps to get to the Final and Implementer's Drafts?<o:p></o:p></p>
<p class="MsoNormal"> Prompt=login parameter language discussion<o:p></o:p></p>
<p class="MsoNormal"> Session management discussion<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Structure of Authentication Section<o:p></o:p></p>
<p class="MsoNormal"> Do we keep current Code/Implicit/Hybrid structure?<o:p></o:p></p>
<p class="MsoNormal"> People agreed to keep the current organization<o:p></o:p></p>
<p class="MsoNormal"> People would like text in the overview saying what the different flows are for<o:p></o:p></p>
<p class="MsoNormal"> Do we move the ID Token definition up?<o:p></o:p></p>
<p class="MsoNormal"> People decided to make the ID Token 2.1<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Review of <a href="http://openid.net/specs/openid-connect-core-1_0.html#HybridIDToken2">
http://openid.net/specs/openid-connect-core-1_0.html#HybridIDToken2</a><o:p></o:p></p>
<p class="MsoNormal"> Say that the OP may choose to return fewer claims about the user from the Authorization Endpoint for privacy reasons, etc.<o:p></o:p></p>
<p class="MsoNormal"> All the claims about the authorization event should be present in both<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Review of <a href="http://openid.net/specs/openid-connect-core-1_0.html#HybridAccessToken2">
http://openid.net/specs/openid-connect-core-1_0.html#HybridAccessToken2</a><o:p></o:p></p>
<p class="MsoNormal"> We will say that they may be the same or may enable different access to resources<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Why do we require POST support at the Authorization Endpoint?<o:p></o:p></p>
<p class="MsoNormal"> <a href="http://openid.net/specs/openid-connect-core-1_0.html#AuthorizationRequest">
http://openid.net/specs/openid-connect-core-1_0.html#AuthorizationRequest</a><o:p></o:p></p>
<p class="MsoNormal"> <a href="http://tools.ietf.org/html/rfc6749#section-3.1">
http://tools.ietf.org/html/rfc6749#section-3.1</a><o:p></o:p></p>
<p class="MsoNormal"> Size considerations, especially when using the "request" parameter<o:p></o:p></p>
<p class="MsoNormal"> Privacy considerations for id_token_hint, etc.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Why are we allowing http redirect_uri values when apparently OAuth doesn’t?<o:p></o:p></p>
<p class="MsoNormal"> <a href="http://tools.ietf.org/html/rfc6749#section-10.5">
http://tools.ietf.org/html/rfc6749#section-10.5</a><o:p></o:p></p>
<p class="MsoNormal"> OP may prevent registration of redirect_uris that do not use https<o:p></o:p></p>
<p class="MsoNormal"> A confidential client needs to be required to use http<o:p></o:p></p>
<p class="MsoNormal"> We will discuss this further on the list<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Why is the id_token_hint recommended for prompt=none?<o:p></o:p></p>
<p class="MsoNormal"> checkid_immediate in OpenID 2.0 worked very well w/o a hint?<o:p></o:p></p>
<p class="MsoNormal"> Describe the meaning of prompt=none with and without id_token_hint<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">"The Authorization Code Flow is suitable for Clients that can securely maintain a Client Secret..."<o:p></o:p></p>
<p class="MsoNormal"> Move to introduction<o:p></o:p></p>
<p class="MsoNormal"> Add sentence saying that the code flow is sometimes also used by Native clients.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Where should the Client Authentication text be?<o:p></o:p></p>
<p class="MsoNormal"> Currently it's Section 8<o:p></o:p></p>
<p class="MsoNormal"> <a href="http://openid.net/specs/openid-connect-core-1_0.html#ClientAuthentication">
http://openid.net/specs/openid-connect-core-1_0.html#ClientAuthentication</a><o:p></o:p></p>
<p class="MsoNormal"> Add forward reference<o:p></o:p></p>
<p class="MsoNormal"> Move to before 5 (parameters as JWTs)<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Introduction<o:p></o:p></p>
<p class="MsoNormal"> This needs to be more finely crafted and be more complete<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Should the "iss", "aud", "redirect_uri", etc. contain a trailing slash?<o:p></o:p></p>
<p class="MsoNormal"> Do we need to say anything?<o:p></o:p></p>
<p class="MsoNormal"> We're already matching these as exact strings<o:p></o:p></p>
<p class="MsoNormal"> Either kinds of strings are acceptable<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Discussion of redirect_uri matching<o:p></o:p></p>
<p class="MsoNormal"> Apparently some are doing wildcard matching in some contexts<o:p></o:p></p>
<p class="MsoNormal"> It's really easy to get this wrong if you don't do exact match<o:p></o:p></p>
<p class="MsoNormal"> There was no appetite for changing this<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">How should the HTTP Form Post text be structured?<o:p></o:p></p>
<p class="MsoNormal"> There was consensus to make this functionality a separate speclet which we take to Implementer's Draft<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Which specs do we make Final and which do we make Implementer's Drafts?<o:p></o:p></p>
<p class="MsoNormal"> Final: Core, Discovery, Registration, Multiple Response Types<o:p></o:p></p>
<p class="MsoNormal"> Implementer's Drafts: Session, HTTP Form Post<o:p></o:p></p>
<p class="MsoNormal"> Do nothing to further approve: Basic, Implicit<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Next steps to get to the Final and Implementer's Drafts?<o:p></o:p></p>
<p class="MsoNormal"> Mike will apply the Core reviews this week, sending e-mail as he goes for points needing discussion<o:p></o:p></p>
<p class="MsoNormal"> We agreed that people will quickly produce reviews for the other three Final specs<o:p></o:p></p>
<p class="MsoNormal"> People are requested to do those reviews by Monday, Oct 28<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Prompt=login parameter language discussion<o:p></o:p></p>
<p class="MsoNormal"> Naveen and Breno described the desire to allow risk-based authentication, rather than password-based authentication<o:p></o:p></p>
<p class="MsoNormal"> In that case, a prompt=login request might not actually prompt the user<o:p></o:p></p>
<p class="MsoNormal"> We will revise the language to talk in terms of affirmative actions to re-authenticate the user<o:p></o:p></p>
<p class="MsoNormal"> And to allow statements about a successful reauthentication to be made in the ID Token<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Session management discussion<o:p></o:p></p>
<p class="MsoNormal"> This didn't occur, but may happen during IIW<o:p></o:p></p>
</div>
</body>
</html>