3 ms·
It saddens me to see OAuth 2.0 in this state. As someone who’s made really minor contributions to 2.0 (and thus listed as a contributor in the spec), I have bee
by rendezvouscp 14y ago
It saddens me to see OAuth 2.0 in this state. As someone who’s made really minor contributions to 2.0 (and thus listed as a contributor in the spec), I have been really looking forward to it being finished and ready for production use (where production use means no more drafts). I stopped following the mailing list last year because most of the threads seemed all too familiar or out of my realm of knowledge to contribute (read: enterprisey).
I run a 1.0a service provider and write clients against it. I’m thinking about wading through the current 2.0 draft, picking out the relevant parts to small startups with an API, and publishing a post about how to implement the sane parts of the 2.0 spec.
- DavidWarden 14y agoPlease do so! I'll help with what I can and little I know.
- Robin_Message 14y agoYes, that would be great, as I'm not sure there are any good docs on writing a OAuth provider.
- ivarkotnik 14y agoI'm in as well.
- vitormazzi 14y agocount me in
- bsenftner 14y agoplease write this up. I gave up trying to figure it out myself.
- berngp 14y agoI am in.
- ejesse 14y agoFWIW, just implementing the server-side version of FB's or Foursquare's implementations will basically get you to the same place.