Actually, to your point 3 Dick, OpenID Connect has defined a simple mechanism
for IdPs to share claims from third parties. Section 4.2 of the Framework
spec<http://openid.net/specs/openid-connect-framework-1_0.html#anchor9> defines
how to represent Aggregated Claims and Distributed Claims, where Aggregated
Claims are third party claims passed by value and Distributed Claims are third
party claims passed by reference.
I agree that having the mechanism is only part of the solution, as a usable
user experience for this functionality is also needed.
-- Mike
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Dick Hardt
Sent: Wednesday, July 20, 2011 6:31 AM
To: Manger, James H
Cc: OpenID Specs Mailing List
Subject: Re: Mozilla BrowserID
John: A user-centric architecture has the user's agent in the middle of
identity transactions. There are some pictures in the slides I show in my short
presentation linked here:
http://dickhardt.org/2010/12/oidf-2010/
In OpenID Connect, the user gives authorizes the RP to call an API at the IdP
to retrieve information about the user. I call this a service-centric model.
There are a number of significant disadvantages of this model:
1) there are unsolved UX challenges to the user seeing what identity data the
RP will get from the IdP.
2) if the user has multiple equivalent attributes, there is no UX for asking
the user which one to provide the RP, so either they are all provided, or just
one. Eg. the user may have multiple postal addresses, and different ones will
be appropriate for different RPs.
3) No simple mechanism has been specified on how the IdP can share claims from
3rd parties. In a user-centric model, the user agent can pull claims from
multiple parties to satisfy an identity request from the user.
James: OpenID Connect does have dynamic client spec:
http://openid.net/specs/openid-connect-registration-1_0.html
Time will tell if any IdP will support it for acquiring identity data. (for
that matter, I have not yet seen any major IdP announce support for OpenID
Connect)
The map that Nat created here:
http://openid.net/2011/07/15/current-map-for-openid-connect/
helps to navigate.
On 2011-07-19, at 11:05 PM, Manger, James H wrote:
>>> As for one of the major advantages of BrowserID: it is a user-centric
>>> architecture unlike OpenID Connect.
>
>> Can you explain what you mean by "user-centric" in this context?
>
>
> With OAuth2 (and hence OpenID Connect, I assume) the RP needs to be
> registered with the IdP. It is not user-centric because the user cannot
> arbitrarily choose an IdP -- they can only choose an IdP with whom the RP is
> registered, which may well mean only one of a handful of major IdPs.
>
> BrowserID is user-centric in that the RP can verify the signature of
> whichever email provider the user chooses. It doesn't rely on a prior
> agreements between the RP and IdP.
>
> --
> James Manger
_______________________________________________
specs mailing list
[email protected]<mailto:[email protected]>
http://lists.openid.net/mailman/listinfo/openid-specs
_______________________________________________
specs mailing list
[email protected]
http://lists.openid.net/mailman/listinfo/openid-specs
