Email Consumer #14

Open
opened 2 years ago by malacoda · 0 comments
malacoda commented 2 years ago
Owner

Provide a way for user to log in to Who Server with an email address. Who Server will send the user an email containing either a login link or an authentication code.

The user can enter their email address directly, or we can delegate to it via RelMeAuth or IndieAuth. In the former case, we should probably fall back to it if the identifier resembles an email address (e.g. sterling@archer.com or mailto:sterling@archer.com). The Who library can probably detect a domain as being an email host but cannot resolve specific accounts on said host (which is probably a good thing).

If the user enters an explicit mailto: URI, it's definitely an email address, although for certain Silo email services with authentication APIs, we can use those instead. This is the approach Portier takes.

Provide a way for user to log in to Who Server with an email address. Who Server will send the user an email containing either a login link or an authentication code. The user can enter their email address directly, or we can delegate to it via RelMeAuth or IndieAuth. In the former case, we should probably fall back to it if the identifier resembles an email address (e.g. `sterling@archer.com` or `mailto:sterling@archer.com`). The Who library can probably detect a domain as being an email host but cannot resolve specific accounts on said host (which is probably a good thing). If the user enters an explicit `mailto:` URI, it's definitely an email address, although for certain Silo email services with authentication APIs, we can use those instead. This is the approach Portier takes.
malacoda added this to the Phase I milestone 2 years ago
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.