Since Google was mentioned here as wanting artifact, let me make the record clear to say that I spoke about artifact binding on my personal capacity.
My very own personal view is that an artifact profile would be easy to spec out (the check_authentication or stateless mode is already the artifact flow without the additional benefits of artifact) and would make OpenID more robust. Currently long URLs require POST which only gives you so much mileage. POST is ugly if the RP has a non-HTTPS endpoint, with scary user confirmation dialogs. Also, I did not wish to express any personal opinion on whether OpenID should seek Loa2, just to note that artifact is the easiest route there. On Thu, Aug 13, 2009 at 10:45 AM, Nat Sakimura<sakim...@gmail.com> wrote: > John, > You changed the topic of this thread. > This thread was about artifact binding, not about Government LoA. > That's another thread :-) > Yes, Artifact helps LoA, but it is not only that. > It helps the mobile space immensely. > =nat > > On Fri, Aug 14, 2009 at 2:00 AM, John Bradley <jbrad...@mac.com> wrote: >> >> Chris >> I think we are agreeing. OpenID needs to play to it's strengths. >> Chasing shiny things is tempting. >> We need to carefully consider the impact of changes. >> That is not to say that openID shouldn't evolve. >> There are always tradeoffs. >> Remember that a GSA LoA 2 or 3 profile is focused on the Gov accepting the >> assertions for specific uses. >> Other people are free to make there own determinations for other use >> cases. >> I am interested in finding out if IdP really want to be certified at LoA 2 >> with all of the extra identity >> proofing, liability and other things that go with that. >> A LoA 2 certification for a IdP involves a lot more than just tweaking >> some protocol peaces. >> Are there OPs that want that? >> John B. >> On 13-Aug-09, at 9:11 AM, Chris Messina wrote: >> >> On Thu, Aug 13, 2009 at 8:34 AM, John Bradley <jbrad...@mac.com> wrote: >>> >>> Some may ask if we add artifact binding, signatures and encryption are we >>> not reinventing SAML Web SSO, or something of equal complexity? >> >> I would like to know more about this, but my instinct is always to say >> "NO" for as long as possible when any new feature will a) introduce >> complexity and b) stifle or impair potential adoption. >> That we've come as far as we have is a feat; maintaining that momentum is >> critical — and that means making good on the promise of what OpenID offers >> *today* — and only extending it with real world examples where people are >> implementing kludges (en masse) to serve a common need. >> >> Chris >> -- >> Chris Messina >> Open Web Advocate >> >> Personal: http://factoryjoe.com >> Follow me on Twitter: http://twitter.com/chrismessina >> >> Citizen Agency: http://citizenagency.com >> Diso Project: http://diso-project.org >> OpenID Foundation: http://openid.net >> >> This email is: [ ] bloggable [X] ask first [ ] private >> >> >> _______________________________________________ >> specs mailing list >> sp...@lists.openid.net >> http://lists.openid.net/mailman/listinfo/openid-specs >> > > > > -- > Nat Sakimura (=nat) > http://www.sakimura.org/en/ > > _______________________________________________ > specs mailing list > sp...@lists.openid.net > http://lists.openid.net/mailman/listinfo/openid-specs > > -- --Breno +1 (650) 214-1007 desk +1 (408) 212-0135 (Grand Central) MTV-41-3 : 383-A PST (GMT-8) / PDT(GMT-7) _______________________________________________ specs mailing list sp...@lists.openid.net http://lists.openid.net/mailman/listinfo/openid-specs
