News for hackers. Stuff that matters.

A comment on Things to Know When Making a Web Application in 2015. Parent comment

Re:Things to Know When Making a Web Application in 2015 by balls187 on Friday July 10, 2015 @03:25PM (#9866199)
1. Why use OAuth unless you want to grant 3rd parties access to your services data, on behalf of your customers?

2. Security best practices subject to "open for interpretation."

[ Parent | on HN ]
Re:Things to Know When Making a Web Application in 2015 by superuser2 on Friday July 10, 2015 @06:23PM (#9867275)
While OAuth isn't "for" authentication, everyone uses it that way by "authorizing" access to "view your email address" which is as good as authenticating your email address.
[ Parent | on HN ]
Re:Things to Know When Making a Web Application in 2015 by balls187 on Friday July 10, 2015 @08:04PM (#9867786)
Can you link to implementations that use OAuth in such a manner?

Login with FB, Google, Github, Twitter, etc different systems, separate from OAuth.

[ Parent | on HN ]
Re:Things to Know When Making a Web Application in 2015 by cpitman on Saturday July 11, 2015 @02:00AM (#9868721)
GitHub How To: https://developer.github.com/guides/basics-of-authentication... And the OpenID Connect standard (essentially OAuth V2 + identity service): http://openid.net/connect/
[ Parent | on HN ]
Re:Things to Know When Making a Web Application in 2015 by hello_there on Friday July 10, 2015 @08:42PM (#9867942)
> Why use OAuth unless you want to grant 3rd parties access to your services data, on behalf of your customers?

So, what would you use instead?

[ Parent | on HN ]
Re:Things to Know When Making a Web Application in 2015 by avinassh on Sunday July 12, 2015 @02:57AM (#9872786)
> Why use OAuth unless you want to grant 3rd parties access to your services data, on behalf of your customers?

Can you explain me this? How Google will be able to access my service data?

[ Parent | on HN ]