OK. I seemed to have screwed up the list of options etc. <div><br></div><div>Also, as the list is terse and it did not include the precise definition of each terms, it led to people talking about different things using the same word. This is another screwing up on my part. </div>
<div><br></div><div>Rather than doing it through mailing list poll, it probably is better to have a call on this issue in a very near future at a time where European participants can also call in, e.g., 11pm JST, 4pm CDT (EU), 10am EDT, 7am PDT. That will let people speak up, explain the meaning, etc. and a whole lot more constructive. Perhaps we should do a doodle poll on the timing. </div>
<div><br></div><div>Nat</div><div><br><div class="gmail_quote">On Thu, Jun 7, 2012 at 4:42 PM, Mike Jones <span dir="ltr"><<a href="mailto:Michael.Jones@microsoft.com" target="_blank">Michael.Jones@microsoft.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">This list left out the possibility that John discussed of having separate scope request values such as email_id that specifically request that sets of scope values be included in the ID Token. (I'm not necessarily in favor of this, but it was discussed at Yahoo and on the list, so should be part of what people react to.)<br>
<br>
This list left out the suggest of Brian's that a different request parameter be defined to act as the switch that the profile, email, address, and phone scope values return claims in the ID Token, rather than the switch being the claims_in_id_token scope. If we're reconsidering all options, this one shouldn't be excluded.<br>
<br>
I don't think there had been any discussion on the list to date since the decisions at Yahoo proposing your option 1b (using a different response type). I've heard people discussing *how* claims should be directed to the ID Token - not *whether* they should be. I hope we don't try to reopen that part of the decision as well, especially because no one has proposed reopening it. As such, I don't believe that it's productive to discuss 1b, 2, or 3b, given that no one has suggested that they are dissatisfied with the option to return claims in the ID token - only the syntax for saying to do it.<br>
<br>
My two cents worth...<br>
<span class="HOEnZb"><font color="#888888"><br>
-- Mike<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
-----Original Message-----<br>
From: <a href="mailto:openid-specs-ab-bounces@lists.openid.net">openid-specs-ab-bounces@lists.openid.net</a> [mailto:<a href="mailto:openid-specs-ab-bounces@lists.openid.net">openid-specs-ab-bounces@lists.openid.net</a>] On Behalf Of Nat Sakimura<br>
Sent: Wednesday, June 06, 2012 11:57 PM<br>
To: Roland Hedberg<br>
Cc: <a href="mailto:openid-specs-ab@lists.openid.net">openid-specs-ab@lists.openid.net</a><br>
Subject: [Openid-specs-ab] Please respond: poll on claims_in_id_token switch in the scope<br>
<br>
I would like to take this issue to a closure quickly.<br>
These issues were discussed at F2F on May 1.<br>
However, that was only among the f2f participant.<br>
I understand the current comments are from those who were not at F2F, and implementers' comments from those implementing it.<br>
I would appreciate a quick response to the following questions so to sum up a bit to help the progress in this issue:<br>
<br>
1. Please indicate which is your preferred way.<br>
<br>
a) Using claims_in_id_token switch in the "scope"<br>
b) Using a new response type.<br>
<br>
Note: on May 1 F2F, 1-a) was chosen. This is how the current draft was prepared. (cf. issue #561)<br>
<br>
2. If 1-b) is chosen, which do you prefer:<br>
<br>
a) A combined response type: e.g., id_token_with_userinfo<br>
b) combination of id_token and userinfo<br>
<br>
3. As a method for returning userinfo claims in the front channel, which do you prefer?<br>
<br>
a) Claims in id_token<br>
b) separate userinfo token with its metadata in id_token?<br>
<br>
Note: At the F2F, a) was chosen.<br>
<br>
Thanks for your cooperation.<br>
<br>
Nat Sakimura<br>
<br>
On 2012/06/07, at 15:29, Roland Hedberg <<a href="mailto:roland.hedberg@adm.umu.se">roland.hedberg@adm.umu.se</a>> wrote:<br>
<br>
><br>
> 7 jun 2012 kl. 07:40 skrev nov matake:<br>
><br>
>> I'm OK with both making single "id_token_with_userinfo" response type or combination of "id_token" and "userinfo".<br>
><br>
><br>
> I'm definitely in favor of the later.<br>
> That is letting 'id_token' contain metadata about the userinfo and the authentication, and 'userinfo' pure user info.<br>
> Similar to the structure of the openid request object.<br>
><br>
> -- Roland<br>
> ------------------------------------------------------<br>
> Roland Hedberg<br>
> IT Architect/Senior Researcher<br>
> ICT Services and System Development (ITS) Umeċ University<br>
> SE-901 87 Umeċ, Sweden<br>
> Phone <a href="tel:%2B46%2090%20786%2068%2044" value="+46907866844">+46 90 786 68 44</a><br>
> Mobile <a href="tel:%2B46%2070%20696%2068%2044" value="+46706966844">+46 70 696 68 44</a><br>
> <a href="http://www.its.umu.se" target="_blank">www.its.umu.se</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><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>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Nat Sakimura (=nat)<div>Chairman, OpenID Foundation<br><a href="http://nat.sakimura.org/" target="_blank">http://nat.sakimura.org/</a><br>@_nat_en</div>
<br>
</div>