Atomic Data introduces a new self-sovereign public key based authentication mechanism. This has its merits (users are in full control of their identity, instead of servers), but pretty much everyone out there already settled on a standard: Open ID Connect. Supporting this helps achieve a few goals:
- Sign in with your existing OIDC account (google, facebook, or your companies SSO server). No need to create a new account!
Thoughts
Libraries Rust
Libraries JS
TODO
Flow
Commits & private key management
If we sign in using some external identity provider, we are redirected to some page. This could be an endpoint that registers a public key to an Agent, adding it to the Agent resource.
Link with email
We're probably not going to be an identity provider, so we can keep things simple. Still, it would make sense to have email support for things like notifications.
But what about signing in using a magic link? Should users be able to add new public keys using email without using OIDC / Oauth? #276
Atomic Data introduces a new self-sovereign public key based authentication mechanism. This has its merits (users are in full control of their identity, instead of servers), but pretty much everyone out there already settled on a standard: Open ID Connect. Supporting this helps achieve a few goals:
Thoughts
Libraries Rust
Libraries JS
TODO
Flow
Commits & private key management
If we sign in using some external identity provider, we are redirected to some page. This could be an endpoint that registers a public key to an Agent, adding it to the Agent resource.
Link with email
We're probably not going to be an identity provider, so we can keep things simple. Still, it would make sense to have email support for things like notifications.
But what about signing in using a magic link? Should users be able to add new public keys using email without using OIDC / Oauth? #276