4 ms·
This is disappointing to hear. For something so important to our immediate future, OAuth 2.0 is currently a mess. There are many different versions of the proto
by apawloski 14y ago
This is disappointing to hear. For something so important to our immediate future, OAuth 2.0 is currently a mess. There are many different versions of the protocol -- some of which aren't backwards compatible -- and losing a leader like this is only going to make the situation worse.
- ecaron 14y agoI think the best hope of getting OAuth back on course is getting the current spec-writers to separately right a mechanism that interfaces with Google, Facebook, Twitter and LinkedIn. After they've each done that, they can get together and talk about how to rectify the train-wreck.
- aaron-lebo 14y agoDo you mind explaining why it is a mess? I'm not doubting what you are saying is true, it is just that recently I used a Clojure library to connect to Facebook, Google, and github, and the code to do so is simple and more or less the same for each site, with one of the sites being slightly different. Is the mess on the side of a library writer's perspective? Or in running it on the server?
- ecaron 14y ago> more or less the same for each site, with one of the sites being slightly different That's because the Clojure library isolated you from the vastly different interpretations that those providers have of the spec. Had you written your connectors from scratch, you would have experienced the "mess."