<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<font face="Helvetica, Arial, sans-serif">Hi John,<br>
<br>
Are you referring to the preferred_username claim of the userinfo
object in the Request Object?<br>
<br>
Thanks,<br>
George<br>
<br>
</font>
<div class="moz-cite-prefix">On 8/29/12 2:12 PM, John Bradley wrote:<br>
</div>
<blockquote
cite="mid:9A1E5354-170B-480A-8A05-ACFDDDA040BD@ve7jtb.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
At the moment we have it as part of the request object. I think
we are coming to the conclusion that it is important enough to
make a parameter for authorization endpoint.
<div><br>
</div>
<div>John <br>
<div>
<div>On 2012-08-29, at 11:27 AM, George Fletcher <<a
moz-do-not-send="true" href="mailto:gffletch@aol.com">gffletch@aol.com</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<meta http-equiv="content-type" content="text/html;
charset=UTF-8">
<div bgcolor="#FFFFFF" text="#000000"> <font
face="Helvetica, Arial, sans-serif">Hi,<br>
<br>
We've run into a case where it would be nice to be able
to pass into the /authorize endpoint a value to pre-fill
the loginid field on the authentication UI. We allow for
an id_token to be passed as a hint of the desired user,
but this only works for an "already authenticated" use
case.<br>
<br>
If we consider the Account Chooser case where what is
stored is the user's email address, it would be nice to
be able to start the identity federation flow passing
that email address along to the IdP. <br>
<br>
Did I just miss support for this in the specs?<br>
<br>
Thanks,<br>
George</font></div>
</blockquote>
</div>
</div>
</blockquote>
<br>
</body>
</html>