OAuth for the Open Web
aaronparecki.com
OAuth for the Open Web
1–10 of 80 posts
Re: OAuth for the Open Web
#2Aaron is one of the cofounders (with Tantek Çelik) of the IndieWeb community.
Re: OAuth for the Open Web
#3I don't understand why the need for this new protocol; what's missing from OpenID?
Re: OAuth for the Open Web
#4I 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?
Re: OAuth for the Open Web
#5Great, 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
#6Persona (https://en.wikipedia.org/wiki/Mozilla_Persona) had it right :(
Re: OAuth for the Open Web
#7Re: OAuth for the Open Web
#8Persona ( https://en.wikipedia.org/wiki/Mozilla_Persona ) had it right :(
Re: OAuth for the Open Web
#9Here are some thoughts for distributed auth:
Re: OAuth for the Open Web
#10I 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.