Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Re: Service warnings for RPs / IDPs
4 views
Skip to first unread message
Peter Williams
May 21, 2012, 8:13:39 PM5/21/12
to Francois Marier, dev-id...@lists.mozilla.org
There Is an inherent tension between Idps and rps.
Does the Idp exist for the benefit of 1, some, all rps? Or vice versa?
One might as well ask: does capital benefit management or labour? above, as it's the same question.
Does the Idp exist to tell n rps when to upgrade (despite their audited change cycle) or does the Idp exist to provide a (mere) authentication service to rp entities?
One senses quickly the assumptions of an initiative.
Browserid seems very "governance" centric. Know thy place, user and relying party. Dont you know (yawn) how hard it is?
One may wish to reconsider.
Sent from my iPhone
On May 21, 2012, at 4:38 PM, "Francois Marier" <fran...@mozilla.com> wrote:
> When you sign up for an API key (e.g. Flickr, Twitter, etc.), the
> organization that you sign up with gets your email and therefore a way
> to get in touch with all of the developers using their APIs. I've also
> seen Open Source projects offer an easy way to "register your site" so
> that you can get be reached if something important comes up.
>
> I can imagine two things about Persona that every RP out there would
> want to know about:
>
> 1- there is a major in the protocol and you need to change your code
> (and/or upgrade the library/plugin you're using) right now
>
> 2- this API has been deprecated and will be removed in 2 months, make
> sure you switch to the new one before then (or upgrade library/plugin)
>
> Maybe it would be useful for us to maintain an optional (but strongly
> recommended) register of users. Something that is so limited in terms of
> traffic that every RP/IDP out there will want to sign up. (It could even
> be the last step of our getting started guide: "Register your site".)
>
> I'm specifically not thinking of an dev-identity-announce list where new
> features and other things would be posted. I think our existing blog is
> fine for that. Instead, what I'm envisioning is something we would use
> only when an action is required on the part of RPs and IDPs.
>
> So if you are an RP or an IDP, does this sound useful to you? Would you
> register/sign-up? Is it too limited (e.g. would you prefer to receive 1
> status email twice a year)? Would you want to be notified of planned or
> unscheduled outages too?
>
> Cheers,
> Francois
> _______________________________________________
> dev-identity mailing list
> dev-id...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-identity
Does the Idp exist for the benefit of 1, some, all rps? Or vice versa?
One might as well ask: does capital benefit management or labour? above, as it's the same question.
Does the Idp exist to tell n rps when to upgrade (despite their audited change cycle) or does the Idp exist to provide a (mere) authentication service to rp entities?
One senses quickly the assumptions of an initiative.
Browserid seems very "governance" centric. Know thy place, user and relying party. Dont you know (yawn) how hard it is?
One may wish to reconsider.
Sent from my iPhone
On May 21, 2012, at 4:38 PM, "Francois Marier" <fran...@mozilla.com> wrote:
> When you sign up for an API key (e.g. Flickr, Twitter, etc.), the
> organization that you sign up with gets your email and therefore a way
> to get in touch with all of the developers using their APIs. I've also
> seen Open Source projects offer an easy way to "register your site" so
> that you can get be reached if something important comes up.
>
> I can imagine two things about Persona that every RP out there would
> want to know about:
>
> 1- there is a major in the protocol and you need to change your code
> (and/or upgrade the library/plugin you're using) right now
>
> 2- this API has been deprecated and will be removed in 2 months, make
> sure you switch to the new one before then (or upgrade library/plugin)
>
> Maybe it would be useful for us to maintain an optional (but strongly
> recommended) register of users. Something that is so limited in terms of
> traffic that every RP/IDP out there will want to sign up. (It could even
> be the last step of our getting started guide: "Register your site".)
>
> I'm specifically not thinking of an dev-identity-announce list where new
> features and other things would be posted. I think our existing blog is
> fine for that. Instead, what I'm envisioning is something we would use
> only when an action is required on the part of RPs and IDPs.
>
> So if you are an RP or an IDP, does this sound useful to you? Would you
> register/sign-up? Is it too limited (e.g. would you prefer to receive 1
> status email twice a year)? Would you want to be notified of planned or
> unscheduled outages too?
>
> Cheers,
> Francois
> _______________________________________________
> dev-identity mailing list
> dev-id...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-identity
0 new messages