We have tried this for a while and the following reasons made us kill it: 1. Email delivery latency: depending on the service you use, the time it takes to deliver emails to the user can vary. Worst case I encountered was up to 20 minutes delay when there were issues with Mailgun. 2. Usability: you have to leave your current app and switch to your mail client. You may be on a device where you don't have a mail client…
4. Email delivery period. Using AWS Simple Email Service, you're actually sharing an email server IP address with other accounts. At times those accounts can get the IP address added to spam lists. All the sudden your emails stop getting received on some clients.* * Solution to this is to pay $$ / month to get a dedicated IP address, then never let it get added to a spam list.
Ask HN: Why aren't one-time sign in links more popular for authentication?
21–30 of 198 posts
Re: Ask HN: Why aren't one-time sign in links more popular for authentication?
#22Earlier quoted context omitted.
We ended up purchasing a dedicated IP from Mailgun. This solves the spam/latency problem mostly, but brings about new problems.
What other problems do you face with a dedicated IP?
I initially thought it was a "problem solved" thing by paying the money. Ended up causing us regular work (not much, but still).
Re: Ask HN: Why aren't one-time sign in links more popular for authentication?
#23Re: Ask HN: Why aren't one-time sign in links more popular for authentication?
#24What about a use case when it is inconvenient to create another password for a new user base at a company and this way you have users without calling support all the time.
Re: Ask HN: Why aren't one-time sign in links more popular for authentication?
#25Imagine that.
Re: Ask HN: Why aren't one-time sign in links more popular for authentication?
#26Re: Ask HN: Why aren't one-time sign in links more popular for authentication?
#27I recently used Vercel’s awesome magic link login. The feature was so awesome that I just needed to open the link in whatever browser. Unfortunately that also means that if I click the link by mistake the bad actor now has full access to my account. All just a misclick away.
> Unfortunately that also means that if I click the link by mistake the bad actor now has full access to my account. All just a misclick away Doesn’t clicking the link set cookies in your browser that then authenticate your session? How would you clicking the link somewhere give access to an attacker?
Some of them recognise that users aren't always signing in on the same device that their email account is set up on, so the link in the email just confirms that the login attempt is genuine.
This is similar to how Google/Apple/Microsoft/Blizzard/Steam handle login requests with their respective authenticator apps. You attempt to log in on device X (which can be anything), then confirm that the login request is genuine on device Y (your personal device).
Re: Ask HN: Why aren't one-time sign in links more popular for authentication?
#28Re: Ask HN: Why aren't one-time sign in links more popular for authentication?
#29It's inconvenient. That's the primary reason why it won't gain mass adoption since any obstacle to your service will lower the registration / engagement metrics. With password managers built into all modern browsers, casual users (which, lets be honest here, are by far the most of the web users) do not have to worry about typing passwords. Security be damned. If it is not invisible to the user, they will reject it.