[Openid-specs-ab] privacy & acr
ve7jtb at ve7jtb.com
Wed Oct 30 01:03:28 UTC 2013
Yes that is perhaps a better way to put it.
I would like to find a way to simplify it but we are getting a bit late in the process.
The option would be to scrap the claims way to ask for required and let people define new acr values that require an exact mach eg loa1-exact-match or something like that.
Adding another query parameter is too ugly.
In general the match parameter for authn context is supposed to control if you are allowed to return better than or exact etc however that never really got used properly as everyone sends exact as the match and then get returned whatever the IdP feels like, on the assumption that if it could not match the request exactly the RP will figure it out from the response.
On Oct 29, 2013, at 9:09 PM, Nat Sakimura <sakimura at gmail.com> wrote:
> RP asking for only LoA 1 and not higher with PPID may not want a LoA2 non-PPID identity as that would require them to go under full PIA. In such a case, the RP may want the request to fail if this acr cannot be fulfilled.
> So, it is not so much for privacy protection but the avoidance of privacy compliance cost.
> =nat via iPhone
> Oct 30, 2013 4:42、Brian Campbell <bcampbell at pingidentity.com> のメッセージ:
>> Yesterday on the call John said that there are privacy reasons to want to be able to request "acr" as an essential claim and return an error if it fails.
>> Can you explain that again John? Who's privacy (I assume the end user's) about what (how/when they authenticated) is being kept from who?
>> Openid-specs-ab mailing list
>> Openid-specs-ab at lists.openid.net
> Openid-specs-ab mailing list
> Openid-specs-ab at lists.openid.net
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 4507 bytes
Desc: not available
More information about the Openid-specs-ab