Run your own OAuth2 server

Re:Run your own OAuth2 server by homakov on Monday September 04, 2017 @03:33PM (#15170364)

If your sole purpose is authentication w/o authorization, one should use securelogin.pw which does not depend on identity provider. And btw OAuth2 spec is insecure by design, it's a known fact.

[ Parent | on HN ]

Re:Run your own OAuth2 server by ForHackernews on Monday September 04, 2017 @03:40PM (#15170395)

> btw OAuth2 spec is insecure by design, it's a known fact.

OAuth2 is only "insecure" in that it relies on TLS for its security: the same as HTTP, IMAP or SMTP. You should never run OAuth2 over a non-HTTPS (i.e. HTTP) connection. The same is true for any other login system.

This is covered in RFC 6819: https://tools.ietf.org/html/rfc6819

[ Parent | on HN ]

Re:Run your own OAuth2 server by homakov on Monday September 04, 2017 @03:42PM (#15170413)

Not just that, a couple of other bad decisions that caused made many websites inherently insecure https://sakurity.com/oauth

[ Parent | on HN ]

Re:Run your own OAuth2 server by machete143 on Monday September 04, 2017 @05:11PM (#15170883)

That is a really bad specification with no examples, no formalization, and zero references.

However, all server-side attack scenarios listed there are not possible with Hydra. Some of them also boil down to misusing OAuth2 for authentication, which is why we have OpenID Connect.

[ Parent | on HN ]

Re:Run your own OAuth2 server by homakov on Monday September 04, 2017 @06:44PM (#15171292)

No, ignore the spec (it's just a list of traits i'd like to suggest), design issues are outlined after it.

[ Parent | on HN ]

Re:Run your own OAuth2 server by ForHackernews on Monday September 04, 2017 @03:46PM (#15170433)

At a glance, this looks like a proprietary re-invention of of https://tools.ietf.org/html/draft-hammer-oauth-v2-mac-token-...

[ Parent | on HN ]