<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:Verdana;
        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;}
pre
        {mso-style-priority:99;
        mso-style-link:"HTML Preformatted Char";
        margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Courier New";}
tt
        {mso-style-priority:99;
        font-family:"Courier New";
        color:#003366;}
span.EmailStyle17
        {mso-style-type:personal-compose;
        font-family:"Calibri","sans-serif";
        color:windowtext;}
span.HTMLPreformattedChar
        {mso-style-name:"HTML Preformatted Char";
        mso-style-priority:99;
        mso-style-link:"HTML Preformatted";
        font-family:"Courier New";}
.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">Per <b><a href="http://openid.net/specs/openid-connect-core-1_0.html#AuthRequest">http://openid.net/specs/openid-connect-core-1_0.html#AuthRequest</a></b>, POST support is mandatory for authentication requests in Connect.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span lang="EN" style="font-family:"Verdana","sans-serif";color:black">Authorization Servers MUST support the use of the HTTP
</span><tt><span lang="EN" style="font-size:10.0pt">GET</span></tt><span lang="EN" style="font-family:"Verdana","sans-serif";color:black"> and
</span><tt><span lang="EN" style="font-size:10.0pt">POST</span></tt><span lang="EN" style="font-family:"Verdana","sans-serif";color:black"> methods defined in
<a href="http://openid.net/specs/openid-connect-core-1_0.html#RFC2616"><span style="text-decoration:none">RFC 2616 (Fielding, R., Gettys, J., Mogul, J., Frystyk, H., Masinter, L., Leach, P., and T. Berners-Lee, “Hypertext Transfer Protocol -- HTTP/1.1,” June 1999.)</span></a>
 [RFC2616] at the Authorization Endpoint. Clients MAY use the HTTP </span><tt><span lang="EN" style="font-size:10.0pt">GET</span></tt><span lang="EN" style="font-family:"Verdana","sans-serif";color:black"> or
</span><tt><span lang="EN" style="font-size:10.0pt">POST</span></tt><span lang="EN" style="font-family:"Verdana","sans-serif";color:black"> methods to send the Authorization Request to the Authorization Server. If using the HTTP
</span><tt><span lang="EN" style="font-size:10.0pt">GET</span></tt><span lang="EN" style="font-family:"Verdana","sans-serif";color:black"> method, the request parameters are serialized using URI Query String Serialization, per
<a href="http://openid.net/specs/openid-connect-core-1_0.html#QuerySerialization">
<span style="text-decoration:none">Section 13.1 (Query String Serialization)</span></a>. If using the HTTP
</span><tt><span lang="EN" style="font-size:10.0pt">POST</span></tt><span lang="EN" style="font-family:"Verdana","sans-serif";color:black"> method, the request parameters are serialized using Form Serialization, per
<a href="http://openid.net/specs/openid-connect-core-1_0.html#FormSerialization">
<span style="text-decoration:none">Section 13.2 (Form Serialization)</span></a>.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN" style="font-family:"Verdana","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal">Per <b><a href="https://tools.ietf.org/html/rfc6749#page-25">https://tools.ietf.org/html/rfc6749#page-25</a></b>, POST support is optional for authorization requests in OAuth 2.0.<o:p></o:p></p>
<pre style="page-break-before:always"><span lang="EN">      The authorization server MUST support the use of the HTTP "GET"<o:p></o:p></span></pre>
<pre style="page-break-before:always"><span lang="EN">      method [<a href="https://tools.ietf.org/html/rfc2616" title=""Hypertext Transfer Protocol -- HTTP/1.1"">RFC2616</a>] for the authorization endpoint and MAY support the use of the "POST" method as well.<o:p></o:p></span></pre>
<pre style="page-break-before:always"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p> </o:p></span></pre>
<p class="MsoNormal">Does anyone remember why we went beyond the OAuth 2.0 requirements in this regard?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">                                                            -- Mike<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>