<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<font face="Helvetica, Arial, sans-serif">Per my action item from
yesterday... here is a possible write up for additional options
for the display parameter. Currently OpenID Connect defines one
value 'none' which means that the request MUST be handled without
showing any UI to the user. Facebook defines (page, iframe,
popup, touch, wap) some of which are also in the OpenID UI
Extension. I'm not sure we want to support iframe so I didn't
include it in the list below. </font><br>
<font face="Helvetica, Arial, sans-serif"><br>
</font>
<blockquote><font face="Helvetica, Arial, sans-serif">page</font><br>
<font face="Helvetica, Arial, sans-serif"> The Authorization
Server SHOULD display authentication and consent UI consistent
with a full browser page view. If the display parameter is not
specified this is the default display mode.</font><br>
<br>
<font face="Helvetica, Arial, sans-serif">popup</font><br>
<font face="Helvetica, Arial, sans-serif"> The Authorization
Server SHOULD display authentication and consent UI consistent
with a popup browser window. The popup browser window SHOULD
conform to N x N pixels.</font><br>
<br>
<font face="Helvetica, Arial, sans-serif">touch</font><br>
<font face="Helvetica, Arial, sans-serif"> The Authorization
Server SHOULD display authentication and consent UI consistent
with a device that leverages a touch interface. The
Authorization Server MAY attempt to detect the device touch and
further customize the interface.</font><br>
<br>
<font face="Helvetica, Arial, sans-serif">wap</font><br>
<font face="Helvetica, Arial, sans-serif"> The Authorization
Server SHOULD display authentication and consent UI consistent
with a "feature phone" type display.</font><br>
</blockquote>
<font face="Helvetica, Arial, sans-serif"><br>
</font><font face="Helvetica, Arial, sans-serif">Note that the
semantics are slightly different as these values are more hints
from the client where as 'none' is a "command". </font><font
face="Helvetica, Arial, sans-serif">Would it make sense to move
the 'none' feature of display to the 'prompt' parameter? It seems
to me that the semantics fit better. The main point of 'none' is
that we don't want to ask the user any questions. The fact that no
UI is displayed is a side effect of not asking the user for any
input.<br>
<br>
</font><font face="Helvetica, Arial, sans-serif">Thanks,<br>
George<br>
</font>
<pre class="moz-signature" cols="72">--
Chief Architect AIM: gffletch
Identity Services Engineering Work: <a class="moz-txt-link-abbreviated" href="mailto:george.fletcher@teamaol.com">george.fletcher@teamaol.com</a>
AOL Inc. Home: <a class="moz-txt-link-abbreviated" href="mailto:gffletch@aol.com">gffletch@aol.com</a>
Mobile: +1-703-462-3494 Blog: <a class="moz-txt-link-freetext" href="http://practicalid.blogspot.com">http://practicalid.blogspot.com</a>
Office: +1-703-265-2544 Twitter: <a class="moz-txt-link-freetext" href="http://twitter.com/gffletch">http://twitter.com/gffletch</a>
</pre>
</body>
</html>