<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Hi Torsten-- N.B.: I don't think I have posting privileges on this list; not sure if the moderator let my previous note through, or if you'll see it simply because I'm sending it directly to you as well...</div><div><br></div><div>As long as the identifier coming from the IdP is "directed" (in OpenID-speak), meaning it makes a different federated identifier for each RP so that multiple RPs can't collude to identify the user on the basis of the IDs they've been given, then that's one issue taken care of. The next issue is whether the identifier itself reveals anything about the user. It's possible to create "directed identities" that are revealing -- e.g., <a href="mailto:bob+rp1@gmail.com">bob+rp1@gmail.com</a>, <a href="mailto:bob+rp2@gmail.com">bob+rp2@gmail.com</a>... But the usual intent with federated identifiers is to make them non-revealing, e.g. "randomstring6234sdfd345" for RP1, etc. Making them explicitly transient as well as pseudonymous also limits the temporal scope of their usefulness, which helps avoid the trap of internal correlation at the RP or collusion with others over time as the pseudonym ages. In SAML, the assumption is that the temporal scope limitation is session-length, to at least allow for things like single logout while protecting against cross-session correlation.</div><div><br></div><div>FWIW,</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>Eve</div><br><div><div>On 1 Dec 2012, at 7:26 AM, Torsten Lodderstedt <<a href="mailto:torsten@lodderstedt.net">torsten@lodderstedt.net</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Hi Eve,<br>
<br>
thanks for pointing this out. At first glance it seems to be feasable although I honestly don't know whether such an identifier would conflict with the OIDC semantics. <br>
<br>
To give you more context: I'm looking for a way to "just" assert a boolean claim to the RP. The use case, I'm currently investigating, is age verification. The RP wants the OP to attest whether the user is above 18. There is no session between RP and OP and the OP will typically not disclose any further data. I would prefer to realize this without the need to make up an identifier just to fulfill the protocol requirements.<br>
<br>
regards,<br>
Torsten.<br><br><div class="gmail_quote"><br>
<br>
Eve Maler <<a href="mailto:eve@xmlgrrl.com">eve@xmlgrrl.com</a>> 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">This sounds just like the justification for SAML's transient pseudonyms -- good only for the current session, handy for cases where the RP needs some sort of unique "handle" for internal user/session management, and useful for session timeouts or single logout a bit later on.<br><br> Eve<br><br>On 30 Nov 2012, at 8:19 AM, Torsten Lodderstedt <<a href="mailto:torsten@lodderstedt.net">torsten@lodderstedt.net</a>> wrote:<br><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;">We don't want the RP to track the user. So we would need to issue different user_id for every request. But I don't think is fit into the Connect philosophy.<br><br>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 #ad7fa8; 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 #8ae234; padding-left: 1ex;">Hi,<br><br>in some cases we want to provide RPs with attributes but no user_id, which is similar to AX. How can this be realized in Connect? The scope value "openid" activates the OpenID mode at the AS but it also requests access to the user_id Claim. If we do not want to disclose a user_id, does this mean we need to define a new, distinct scope for our use case, e.g. "attribute_x"?<br><br>regards,<br>Torsten.<br><hr><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">http://lists.openid.net/mailman/listinfo/openid-specs-ab</a></blockquote><br></blockquote><hr><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">http://lists.openid.net/mailman/listinfo/openid-specs-ab</a></blockquote><br><br>Eve Maler <a href="http://www.xmlgrrl.com/blog">http://www.xmlgrrl.com/blog</a><br>+1 425 345 6756 <a href="http://www.twitter.com/xmlgrrl">http://www.twitter.com/xmlgrrl</a><br><br><br></pre></blockquote></div></blockquote></div><br><div apple-content-edited="true">
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="font-family: Courier; "><br class="Apple-interchange-newline">Eve Maler <a href="http://www.xmlgrrl.com/blog">http://www.xmlgrrl.com/blog</a><br>+1 425 345 6756 <a href="http://www.twitter.com/xmlgrrl">http://www.twitter.com/xmlgrrl</a><br><br></span></span>
</div>
<br></body></html>