dolu on Nostr: Ok, it's an oauth2 login flow. When you "Login with Google/Apple/Github/..." it uses ...

Ok, it's an oauth2 login flow. When you "Login with Google/Apple/Github/..." it uses the protocol Oauth2.

Instead of having Google/Apple/... as source of identity, nostr can be this source of identity. It's "Login with Nostr" protocol for traditional websites (TIDAL could uses this for example)

quoting
note15pq…d32g

Should I revive zerologin.co?

It was an LNURL-Auth authentication server using a custom login flow.

I have had something new in mind for a few months and I've decided to share this on Nostr after reading this article https://hivemind.vc/identity/ from Max (npub18lz…ugm3)

🎯 Adding Nostr as a source of identity using OAuth2 + OpenID Connect flow.

1- Service.com asks for login using OAuth2 with Google, Twitter, ..., Nostr (through Zerologin.co).
2 - User chooses Nostr, gets redirected to zerologin.co with an OAuth2 login flow.
3 - Instead of typing email + password (like using Google if not already connected), User can log in using Nostr (NIP-98, bunker, or any other methods).
4 - Zerologin redirects back to service.com with an authenticated token.

It's not for a Nostr app like Primal, Coracle, etc.
This service should be used by traditional services where accounts are managed by the service itself.

What do you think? Nostr as identity for traditional websites

Zerologin could also still be usable with LNURL-Auth with this Oauth2 flow.