<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:12.0pt;
font-family:"Times New Roman","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;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.hoenzb
{mso-style-name:hoenzb;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.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"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I’d be fine with that. Why don’t you file an issue to track this and we can approve the note on tomorrow’s call.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> -- Mike<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<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""> Nat Sakimura [mailto:sakimura@gmail.com]
<br>
<b>Sent:</b> Wednesday, January 30, 2013 7:34 PM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> Tim Bray; openid-specs-ab@lists.openid.net<br>
<b>Subject:</b> Re: [Openid-specs-ab] Behavior if the scope parameter is omitted<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">At the same time, though, as a best practice, we could recommend "openid" be the first in the list of scopes, I guess, perhaps in a "Note:". <o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Nat<o:p></o:p></p>
<div>
<p class="MsoNormal">2013/1/31 Mike Jones <<a href="mailto:Michael.Jones@microsoft.com" target="_blank">Michael.Jones@microsoft.com</a>><o:p></o:p></p>
<p class="MsoNormal"><a href="http://openid.net/specs/openid-connect-messages-1_0.html#scopes" target="_blank">http://openid.net/specs/openid-connect-messages-1_0.html#scopes</a>,
<a href="http://openid.net/specs/openid-connect-basic-1_0.html#scopes" target="_blank">
http://openid.net/specs/openid-connect-basic-1_0.html#scopes</a>, and <a href="http://openid.net/specs/openid-connect-implicit-1_0.html#scopes" target="_blank">
http://openid.net/specs/openid-connect-implicit-1_0.html#scopes</a> - "openid" scope is REQUIRED. Pretty unambiguous.<br>
<br>
We don't say that it should be first, since OAuth says that they're order-independent.<br>
<span style="color:#888888"><br>
<span class="hoenzb"> -- Mike</span></span><o:p></o:p></p>
<div>
<p class="MsoNormal"><br>
-----Original Message-----<br>
From: Tim Bray [mailto:<a href="mailto:tbray@textuality.com">tbray@textuality.com</a>]<br>
Sent: Wednesday, January 30, 2013 2:15 PM<br>
To: Mike Jones<o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal">Cc: Amanda Anganes; <a href="mailto:openid-specs-ab@lists.openid.net">
openid-specs-ab@lists.openid.net</a><br>
Subject: Re: [Openid-specs-ab] Behavior if the scope parameter is omitted<br>
<br>
Coincidentally I was just arguing with an implementer here who was being sloppy about leaving out the "openid..." in the scope, and I was wishing there were unambiguous language saying that "scope MUST be present and MUST begin with the token 'openid'", that
I could use to beat this person over the head. Seems like that's what any sane person would do anyhow. -T<br>
<br>
On Wed, Jan 30, 2013 at 2:07 PM, Mike Jones <<a href="mailto:Michael.Jones@microsoft.com">Michael.Jones@microsoft.com</a>> wrote:<br>
> Technically, the Connect specs are silent on what should happen if the<br>
> "openid" scope value isn't present. The server could do anything that<br>
> it and its clients decide to do (including behaving as if the "openid"<br>
> scope value were present). Omitting it isn't a good practice, however.<br>
><br>
><br>
><br>
> --<br>
> Mike<br>
><br>
><br>
><br>
> From: <a href="mailto:openid-specs-ab-bounces@lists.openid.net">openid-specs-ab-bounces@lists.openid.net</a><br>
> [mailto:<a href="mailto:openid-specs-ab-bounces@lists.openid.net">openid-specs-ab-bounces@lists.openid.net</a>] On Behalf Of Amanda<br>
> Anganes<br>
> Sent: Wednesday, January 30, 2013 2:01 PM<br>
> To: <a href="mailto:openid-specs-ab@lists.openid.net">openid-specs-ab@lists.openid.net</a><br>
> Subject: [Openid-specs-ab] Behavior if the scope parameter is omitted<br>
><br>
><br>
><br>
> The OAuth 2.0 Specification, in section 3.3, says the following [1]:<br>
><br>
> If the client omits the scope parameter when requesting<br>
> authorization, the authorization server MUST either process the<br>
> request using a pre-defined default value or fail the request<br>
> indicating an invalid scope. The authorization server SHOULD<br>
> document its scope requirements and default value (if defined).<br>
><br>
> Messages section 2.4 [2] does not give any additional guidance about<br>
> what to do if the client does not specify a scope value when making a<br>
> request; however, it does indicate that the "openid" scope value MUST<br>
> be included for the request to be treated as an OpenID Connect request<br>
> (rather than an OAuth<br>
> 2.0 request).<br>
><br>
> What is the server required/allowed to do if the client omits to send<br>
> the scope parameter? Does that MUST disallow an OIDC server from<br>
> defaulting a non-scoped request to include the "openid" scope?<br>
><br>
> [1] <a href="http://tools.ietf.org/html/rfc6749#section-3.3" target="_blank">http://tools.ietf.org/html/rfc6749#section-3.3</a><br>
> [2] <a href="http://openid.net/specs/openid-connect-messages-1_0.html#scopes" target="_blank">
http://openid.net/specs/openid-connect-messages-1_0.html#scopes</a><br>
><br>
> --Amanda<br>
><br>
><br>
> _______________________________________________<br>
> Openid-specs-ab mailing list<br>
> <a href="mailto:Openid-specs-ab@lists.openid.net">Openid-specs-ab@lists.openid.net</a><br>
> <a href="http://lists.openid.net/mailman/listinfo/openid-specs-ab" target="_blank">
http://lists.openid.net/mailman/listinfo/openid-specs-ab</a><br>
><br>
_______________________________________________<br>
Openid-specs-ab mailing list<br>
<a href="mailto:Openid-specs-ab@lists.openid.net">Openid-specs-ab@lists.openid.net</a><br>
<a href="http://lists.openid.net/mailman/listinfo/openid-specs-ab" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs-ab</a><o:p></o:p></p>
</div>
</div>
</div>
<p class="MsoNormal"><br>
<br clear="all">
<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">-- <br>
Nat Sakimura (=nat)<o:p></o:p></p>
<div>
<p class="MsoNormal">Chairman, OpenID Foundation<br>
<a href="http://nat.sakimura.org/" target="_blank">http://nat.sakimura.org/</a><br>
@_nat_en<o:p></o:p></p>
</div>
</div>
</div>
</body>
</html>