Mozilla BrowserID

Nat Sakimura sakimura at gmail.com
Wed Jul 20 16:46:25 UTC 2011


On Wed, Jul 20, 2011 at 1:05 PM, Manger, James H <
James.H.Manger at team.telstra.com> 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.
>

FYI, OpenID Connect supports dynamic registration of the client, though
whether the IdP supports the feature or not is an entirely different
question. Even in OpenID 2.0, there were IdPs who were white listing the
RPs.


>
> 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
> specs at lists.openid.net
> http://lists.openid.net/mailman/listinfo/openid-specs
>



-- 
Nat Sakimura (=nat)
Chairman, OpenID Foundation
http://nat.sakimura.org/
@_nat_en
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs/attachments/20110721/5a454416/attachment.html>


More information about the specs mailing list