IndieAuth VS OAuth

IndieAuth[1] is a slick DNS-based approach. Maybe offering that as a service would be a nice alternative. I point my DNS to you, and you handle authentication for everything that uses IndieAuth. If you go away or I don't like what you're doing then I can point my DNS to someone else offering that service and I retain the same DNS identity, and ability to use it to login anywhere I've set it up as my identity.... - Source: Hacker News / over 1 year ago

This is interesting but doing it the other way around - HN using something like IndieAuth[0] to verify user account identities without holding PII on the site itself - might be even more useful. [0]https://indieauth.com/. - Source: Hacker News / over 2 years ago

You want OAuth. You almost certainly want to use Keycloak as your provider. Source: 9 months ago

It's the same as when you get "log in with Google" or "Log in with Facebook" buttons on other sites. You can read about OpenAuth here: https://oauth.net/. Source: 10 months ago

Failure to adhere strictly to battle-tested standards like OAuth or OpenID Connect (OIDC). - Source: dev.to / 10 months ago

In addition to user authentication, BudPay secures its API endpoints using authentication mechanisms such as API keys and OAuth (Open Authorization). These mechanisms ensure that only authorized applications and services can access BudPay's APIs, protecting user data from unauthorized access. - Source: dev.to / 11 months ago

You'll typically need a way for users to authenticate to the service – probably using OAuth if you want them to login with their accounts from an identity provider, such as Google or Facebook. Source: over 1 year ago