<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 20-Jan-14<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">Tim Bray<o:p></o:p></p>
<p class="MsoNormal">Nat Sakimura<o:p></o:p></p>
<p class="MsoNormal">Todd Lainhart - Rational software at IBM<o:p></o:p></p>
<p class="MsoNormal"> Building OpenSSO server based on Connect<o:p></o:p></p>
<p class="MsoNormal"> Interfacing with WebSphere people who are also interested in Connect<o:p></o:p></p>
<p class="MsoNormal">Brian Campbell<o:p></o:p></p>
<p class="MsoNormal">Edmund Jay<o:p></o:p></p>
<p class="MsoNormal">Naveen Agarwal<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"> Potential changes to session management for multiple logins<o:p></o:p></p>
<p class="MsoNormal"> Open Issues<o:p></o:p></p>
<p class="MsoNormal"> Session State<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Potential changes to session management for multiple logins:<o:p></o:p></p>
<p class="MsoNormal"> Naveen opened the discussion by sharing some of his/Google's thoughts<o:p></o:p></p>
<p class="MsoNormal"> Google believes that signing out on relying party doesn't make a lot of sense in consumer use cases<o:p></o:p></p>
<p class="MsoNormal"> Google would like to see switch user options for multiple logins<o:p></o:p></p>
<p class="MsoNormal"> IdPs can decide whether to support a global logout<o:p></o:p></p>
<p class="MsoNormal"> Switch user kills local cookies, but leaves user signed into IdP<o:p></o:p></p>
<p class="MsoNormal"> Google has an authorization endpoint parameter to force showing the Account Chooser<o:p></o:p></p>
<p class="MsoNormal"> A different prompt parameter<o:p></o:p></p>
<p class="MsoNormal"> John & Brian pointed out the select_account parameter<o:p></o:p></p>
<p class="MsoNormal"> This may be what Google is already using<o:p></o:p></p>
<p class="MsoNormal"> Google's logout widget currently just deletes their local cookies<o:p></o:p></p>
<p class="MsoNormal"> It doesn't use any endpoints<o:p></o:p></p>
<p class="MsoNormal"> Naveen thinks that the current logout interfaces will work fine for IdPs that support global logout<o:p></o:p></p>
<p class="MsoNormal"> IBM had proprietary extensions to OAuth 2.0 for logout<o:p></o:p></p>
<p class="MsoNormal"> The IdP would send logout messages to registered RPs<o:p></o:p></p>
<p class="MsoNormal"> IBM has switched to OpenID Connect<o:p></o:p></p>
<p class="MsoNormal"> They still have the server side notifications in place for now<o:p></o:p></p>
<p class="MsoNormal"> Edmund's PHP and Scala implementations both implement session management<o:p></o:p></p>
<p class="MsoNormal"> No one appears to be proposing changes, at least on the call<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"> #914: Session 5 - Missing client_id parameter<o:p></o:p></p>
<p class="MsoNormal"> People seem to be in favor of including this parameter<o:p></o:p></p>
<p class="MsoNormal"> Some said that the RP may not still have access to the ID Token<o:p></o:p></p>
<p class="MsoNormal"> Todd asked whether any state can be round tripped across a logout<o:p></o:p></p>
<p class="MsoNormal"> We don't support that directly<o:p></o:p></p>
<p class="MsoNormal"> Registering multiple post-logout pages can be used to pass some state<o:p></o:p></p>
<p class="MsoNormal"> We would need to add security considerations about the client_id being spoofable<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Session State:<o:p></o:p></p>
<p class="MsoNormal"> There was a discussion of the Session State computation<o:p></o:p></p>
<p class="MsoNormal"> It's not clear how to determine the client origin<o:p></o:p></p>
<p class="MsoNormal"> It might be the same hostname as the redirect_uri, but that's not always true<o:p></o:p></p>
<p class="MsoNormal"> We may need to register the client origin explicitly<o:p></o:p></p>
<p class="MsoNormal"> Todd will file an issue about this<o:p></o:p></p>
</div>
</body>
</html>