<html><head/><body><html><head></head><body>Do you mean there is effectively no difference between PPID and no user id since the RP can anyway recognize the user?<br>
<br>
regards,<br>
Torsten.<br><br><div class="gmail_quote"><br>
<br>
John Bradley <ve7jtb@ve7jtb.com> schrieb:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre style="white-space: pre-wrap; word-wrap:break-word; font-family: sans-serif; margin-top: 0px">That could easily be done in the current spec.<br /><br />I don't quite know why PPID won't work for you though.<br /><br /><br />On 2012-12-01, at 2:35 PM, Torsten Lodderstedt <torsten@lodderstedt.net> wrote:<br /><br /><br /><br /><br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;">What sort of tracking are you trying to stop?<br /><br />If it is give me an attribute for the current person without<br />establishing a session that would be an ephemeral single use<br />identifier. (No session management)</blockquote><br />That's what I want. Would this require a new user id type?<br /><br />Setting this per client id is fine.<br /><br />Regards,<br />Torsten.<br /><br /><blockquote
class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;">If you want to have a session with the person based on claims but not<br />establish a persistent account then it would be per session ephemeral. <br />(session management/ change user is possible)<br /><br />user_id_type in registration allows the identifier type to be set per<br />client.<br /><br />We talked about having it in the request object, but allowing a client<br />to change it per request was seen as overkill.<br />Most IdP will restrict what a client can ask for based on some privacy<br />policy, so the discovery/registration mechanism was thought to be<br />sufficient.<br /><br />Nothing stops a site from having multiple client ID if it needs to get<br />different identifier types. Having the different client ID stops a<br />client from asking for PPID and getting connect and then asking for a<br />public identifier in a later call where the user is not
notified.<br /><br />John B.<br />On 2012-11-30, at 1:19 PM, Torsten Lodderstedt<br /><torsten@lodderstedt.net> wrote:<br /><br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #8ae234; padding-left: 1ex;">We don't want the RP to track the user. So we would need to issue<br /></blockquote>different user_id for every request. But I don't think is fit into the<br />Connect philosophy.<br /><br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #8ae234; padding-left: 1ex;">regards,<br />Torsten.<br /><br />Am 30.11.2012 17:11, schrieb Justin Richer:<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #fcaf3e; padding-left: 1ex;">Would using pairwise identifiers make this work?<br /><br />-- Justin<br /><br />On 11/30/2012 11:09 AM, Torsten Lodderstedt wrote:<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid
#e9b96e; padding-left: 1ex;">Hi,<br /><br />in some cases we want to provide RPs with attributes but no<br /></blockquote></blockquote></blockquote>user_id, which is similar to AX. How can this be realized in Connect?<br />The scope value "openid" activates the OpenID mode at the AS but it<br />also requests access to the user_id Claim. If we do not want to<br />disclose a user_id, does this mean we need to define a new, distinct<br />scope for our use case, e.g. "attribute_x"?<br /><br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #8ae234; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #fcaf3e; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #e9b96e; padding-left: 1ex;">regards,<br />Torsten.<br /><hr /><br />Openid-specs-ab mailing list<br />Openid-specs-ab@lists.openid.net<br /><a
href="http://lists.openid.net/mailman/listinfo/openid-specs-ab">http://lists.openid.net/mailman/listinfo/openid-specs-ab</a></blockquote><br /></blockquote><hr /><br />Openid-specs-ab mailing list<br />Openid-specs-ab@lists.openid.net<br /><a href="http://lists.openid.net/mailman/listinfo/openid-specs-ab">http://lists.openid.net/mailman/listinfo/openid-specs-ab</a></blockquote><br /><br /></blockquote></blockquote></pre></blockquote></div></body></html></body></html>