3 ms·

Why not OpenID Connect? Not only does it have discovery for OAuth2 endpoints, it also specifies how to discovery the OIDC endpoint from a bare domain and userna

Why not OpenID Connect? Not only does it have discovery for OAuth2 endpoints, it also specifies how to discovery the OIDC endpoint from a bare domain and username via WebFinger. It also has extensions for dynamic client registration, supports flows that work with input-restricted clients, as well as single page apps, and the UserInfo endpoint. And it's also already implemented and supported in lots of places. There are tools like Dex that offer OIDC and can use "upstream" OIDC providers for the actual user management. I'm not getting why IndieAuth is needed beyond what OIDC offers? Also, for those mentioning Persona/BrowserID/Portier, it is an OpenID Connect provider, and I've just recently sent PRs for it and Dex that allow them to work together.

dane-pgp 8y ago
> Why not OpenID Connect? Someone asked that in the comments of the article and the author responded with this link: https://indieweb.org/indieauth-vs-openid-connect https://indieweb.org/indieauth-vs-openid-connect The answer seems to boil down to IndieAuth being more decentralized.
- colemickens 8y ago
  Aha, one more bit of indirection ala OpenID v1 to make the base identity portable. I like it. Thanks for the link!
- user5994461 8y ago
  Not at all. The answer is that the guy is pushing for his own product and company.
  - floatboth 8y ago
    There is no company and product, there is a community and open specifications.
  - detaro 8y ago
    The author works for a company in the Auth space, but said company has no products based on this specification, and it was created prior to him working there.