Ask HN: What type of Auth are you using on your side projects?
41–50 of 72 posts
Re: Ask HN: What type of Auth are you using on your side projects?
#42Email+password, jwt tokens. Nothing fancy.
Re: Ask HN: What type of Auth are you using on your side projects?
#43Re: Ask HN: What type of Auth are you using on your side projects?
#44I've been in big tech and out of touch with the real world for a while, and I started a project only a couple of weeks ago to get a feel for what the cool kids are doing in web dev in 2024. So I can't claim any deep authority or experience with a lot of different approaches. But I picked Clerk because it was in a tutorial, and so far so good. It couldn't have been much easier, and the free tier seems more than genero…
Certainly understandable to worry about lock-in! We do try and make data exports as easy as possible. You can use our Backend API directly to retrieve all data for your users except for passwords: https://clerk.com/docs/reference/backend-api/tag/Users#opera...
If you need encrypted passwords in the export, you can contact our support team who will verify your account and provide a link from within your Clerk Dashboard to download the complete export directly.
Re: Ask HN: What type of Auth are you using on your side projects?
#45This is the absolutely simplest of authentication (not authorization) schemes I've used that is both easy for people to use and prevents the simplest of spam/robots: - Be able to store two types of tokens, one that is temporary, and one that is "permanent" - Users can use their email address to get sent a temporary token (which expires if unused after X minutes) - Users can click that link to change the temporary tok…
I personally just really don't like magic links auth. It just feels brittle and if your email provider attempts to scan urls to see where they actually go you end up giving them an auth token and by the time the user clicks the link it's invalidated (or you don't invalidate the link at all which is worse). If you have an issue with bots on your platform you're going to always have bot problems. It's trivial to abuse…
One way you can handle this is to place the token in the hash portion of the url (which doesn't get sent to servers during an HTTP request), and then have JS on the frontend send the token to your backend manually. As long as the email provider isn't scanning links via a headless browser that executes JS, this should work.
I agree with your point about email abuse though (although you still have to prevent bots from abusing email based password resets).
Re: Ask HN: What type of Auth are you using on your side projects?
#46Just some ip based rate limits.
Ban misbehaved bot ip addresses.
https://hn.garglet.com (advanced search for hacker news)
Re: Ask HN: What type of Auth are you using on your side projects?
#47Keycloak or auth0. The app should support oauth2, if it does not it gets traefik-forward-auth (or whatever it’s called) to enforce mfa then you are in. There are tons of open source projects to complete the self service experience, from sign up systems to self service password resets
Keycloak has too many new major releases. It is a real pain to keep up with.
Re: Ask HN: What type of Auth are you using on your side projects?
#48Re: Ask HN: What type of Auth are you using on your side projects?
#49Re: Ask HN: What type of Auth are you using on your side projects?
#50Keycloak or auth0. The app should support oauth2, if it does not it gets traefik-forward-auth (or whatever it’s called) to enforce mfa then you are in. There are tons of open source projects to complete the self service experience, from sign up systems to self service password resets