News for hackers. Stuff that matters.
Re:OAuth Security Cheatsheet by stormbrew on Monday May 12, 2014 @06:37PM (#7735797)
The place I work for deals with about 20 different site's oauth processes and it's amazing how widely varied they are. Some of them let you restrict the redirect_uri while others don't, some of them still need you to send a login/password pair for the first request rather than do an oauth flow, but then still use oauth-style tokens all over the place. A couple of them require that the token be passed as a query string parameter instead of as a header for all requests. Being responsibly secure with all of them is quite difficult. It doesn't help that it's very difficult to have a development environment work properly with them, so doing active work against them is often painful.

OAuth is basically a complete mess, implementation-wise, and that's really sad since it's such a promising and useful premise.

Re:OAuth Security Cheatsheet by MAGZine on Monday May 12, 2014 @09:34PM (#7736249)
That's really unfortunate. I read through the RFC, and IIRC it is pretty consistent on those details. Can't stop people from badly implementing a spec :(
Re:OAuth Security Cheatsheet by fnom on Tuesday May 13, 2014 @05:54AM (#7737304)
i've heard great stuff about oauth.io . they try to provide an abstractionlayer that handles the various different implementations (often buggy or not to spec) of oauth.
Re:OAuth Security Cheatsheet by indeyets on Tuesday May 13, 2014 @06:29AM (#7737408)
that might be true, but I don't like idea of having a MiTM. That's an additional point of potential security issues
Re:OAuth Security Cheatsheet by fnom on Tuesday May 13, 2014 @07:51AM (#7737618)
i think its fully open source[1] and you can host on your own

[1]https://github.com/oauth-io/oauthd