<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><p class="MsoNormal"><font face="UICTFontTextStyleBody" size="3"><span style="background-color: rgba(255, 255, 255, 0);">FYI, after the call, Brian, John and me discussed this a bit more, and came to the conclusion that returning auth_time=0 may also be a good. There are times that you really do not know what it was, and in that case, returning the epic would be a reasonable thing. In google's case, it can always return auth_time=0 when asked indicating that google is unwilling to disclose this data. <o:p></o:p></span></font></p><div><p class="MsoNormal"><o:p style="background-color: rgba(255, 255, 255, 0);"><font face="UICTFontTextStyleBody" size="3"> </font></o:p></p></div><div><p class="MsoNormal"><font face="UICTFontTextStyleBody" size="3"><span style="background-color: rgba(255, 255, 255, 0);">So, the semantics of auth_time=0 is either the IdP does not know the last active authentication time or is not willing to disclose it for various policy reasons, including both security and privacy. </span></font></p></div><br>=nat via iPhone</div><div><br>2015/03/26 9:54、Mike Jones <<a href="mailto:Michael.Jones@microsoft.com">Michael.Jones@microsoft.com</a>> のメッセージ:<br><br></div><blockquote type="cite"><div>
<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]-->
<div class="WordSection1">
<p class="MsoNormal">Spec call notes 26-Mar-15<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">Brian Campbell<o:p></o:p></p>
<p class="MsoNormal">Nat Sakimura<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">Justin Richer<o:p></o:p></p>
<p class="MsoNormal">Roland Hedberg<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"> UserInfo access passing access token in the body<o:p></o:p></p>
<p class="MsoNormal"> Google not wanting to support max_age and auth_time<o:p></o:p></p>
<p class="MsoNormal"> JOSE/JWT/OAuth Assertions specs 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"> #123: redirect_URI tests still reporting wrong results.<o:p></o:p></p>
<p class="MsoNormal"> John will close as resolved<o:p></o:p></p>
<p class="MsoNormal"> No other issues were immediately pertinent to certification<o:p></o:p></p>
<p class="MsoNormal"> Mike has placed two issues not needed for v1 certification on hold<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">UserInfo access passing access token in the body<o:p></o:p></p>
<p class="MsoNormal"> It's a MAY in 6750<o:p></o:p></p>
<p class="MsoNormal"> This there to enable JavaScript clients and others which may not be able add an Authorization header<o:p></o:p></p>
<p class="MsoNormal"> Let's make this a WARNING rather than an ERROR now<o:p></o:p></p>
<p class="MsoNormal"> In v2, we should probably add this to the Dynamic profile as required<o:p></o:p></p>
<p class="MsoNormal"> Roland will make this a warning and send a note to the list when it's done<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Google not wanting to support max_age and auth_time<o:p></o:p></p>
<p class="MsoNormal"> Possibly reply asking if they can return an auth_time that actually reflects when the user authorized/was in possession of the device<o:p></o:p></p>
<p class="MsoNormal"> User presence signal that doesn't require a password<o:p></o:p></p>
<p class="MsoNormal"> Such as a native application on a mobile device<o:p></o:p></p>
<p class="MsoNormal"> A screen unlock is a valid user presence indicator<o:p></o:p></p>
<p class="MsoNormal"> But device authentication time is a different semantic, which could be added, but it's different<o:p></o:p></p>
<p class="MsoNormal"> Reauthentication may make more sense in the context of a particular action by the user<o:p></o:p></p>
<p class="MsoNormal"> Real-time consent for an action, as a step-up action, rather than just re-login<o:p></o:p></p>
<p class="MsoNormal"> Then the user has context for the action<o:p></o:p></p>
<p class="MsoNormal"> Mike will send a response asking for more discussion<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">JOSE/JWT/OAuth Assertions specs status<o:p></o:p></p>
<p class="MsoNormal"> These have exited RFC Editor "EDIT" status<o:p></o:p></p>
<p class="MsoNormal"> They are now in "RFC-EDITOR" status: Undergoing final internal review before AUTH48
<o:p></o:p></p>
<p class="MsoNormal"> This means the authors will soon be asked to verify that the edited specs are correct<o:p></o:p></p>
<p class="MsoNormal"> This is called AUTH48 because authors are supposed to respond within 48 hours<o:p></o:p></p>
</div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>Openid-specs-ab mailing list</span><br><span><a href="mailto:Openid-specs-ab@lists.openid.net">Openid-specs-ab@lists.openid.net</a></span><br><span><a href="http://lists.openid.net/mailman/listinfo/openid-specs-ab">http://lists.openid.net/mailman/listinfo/openid-specs-ab</a></span><br></div></blockquote></body></html>