Live data from Hacker News

OAuth for the Open Web

aaronparecki.com

1–10 of 80 posts

Re: OAuth for the Open Web

#5
Great, it’s de-centralized OAuth. All we need now is a replacement for the hideous URL login prompt. My preference would be for an AccountChooser-style list of accounts you’ve recently used so you can pick one and sign in—and enter a URL (or email) only if you need to.

Re: OAuth for the Open Web

#7
post #4

I don't understand why the need for this new protocol; what's missing from OpenID?

OpenID doesn't provide API access like OAuth does, does it?

Exactly, it doesn't. Instead, OpenID had tons of weird bloat no one ever needed. XRI, XRDS, Yadis, WTF

Re: OAuth for the Open Web

#10
post #4

I don't understand why the need for this new protocol; what's missing from OpenID?

OpenID doesn't provide API access like OAuth does, does it?

From Wikipedia : "the third generation of OpenID technology, OpenID Connect, is an authentication layer that sits on top of the OAuth 2.0 authorization framework.[82] It allows computing clients to verify the identity of an end-user based on the authentication performed by an authorization server, as well as to obtain the basic profile information about the end-user in an interoperable and REST-like manner. In technical terms, OpenID Connect specifies a RESTful HTTP API, using JSON as a data format. OpenID Connect allows a range of organizations, including web-based, mobile and JavaScript clients, to request and receive information about authenticated sessions and end-users".

My favorite implementation: Keycloak.

Post reply on HN