i use lucia in svelte.
Ask HN: What type of Auth are you using on your side projects?
61–70 of 72 posts
Re: Ask HN: What type of Auth are you using on your side projects?
#62Keycloak 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
Is Keycloak really appropriate for a side-project? Seems quite complex AFAICT.
you might be right. I also run freeipa on the backside to manage auth for all of my infra. Maybe I enjoy the flexibility.
For me the complexity only comes out when things malfunction. However, the MTBF outweighs the MTTR
Re: Ask HN: What type of Auth are you using on your side projects?
#63Django allauth, 10 years later still a no-brainer. For selfhosting Authentik + Traefik forward auth is a unbeatable combo
Allauth is great. It has so many feature flags for all the microdecisions you want to tune. Social account merges with email account or not... it is configurable! Email confirmation required? Configurable! And it just works.
Re: Ask HN: What type of Auth are you using on your side projects?
#64no auth at all
Haha, that's the best way to do it if you can swing it. It's like writing no code. Unfortunately many apps tie data to users and need to persist it across devices, which makes some kind of login functionality required.
I wonder how many apps could get by being front end only (static site) and delegating auth+storage to dropbox (and similar).
Re: Ask HN: What type of Auth are you using on your side projects?
#65Earlier quoted context omitted.
Haha, that's the best way to do it if you can swing it. It's like writing no code. Unfortunately many apps tie data to users and need to persist it across devices, which makes some kind of login functionality required.
I wonder how many apps could get by being front end only (static site) and delegating auth+storage to dropbox (and similar).
Yeah, that's a good question. Did the jamstack folks solve this?
https://www.reddit.com/r/JAMstack_dev/comments/haf3h0/user_a... seems interesting in this context.
Re: Ask HN: What type of Auth are you using on your side projects?
#66no auth at all
Haha, that's the best way to do it if you can swing it. It's like writing no code. Unfortunately many apps tie data to users and need to persist it across devices, which makes some kind of login functionality required.
it can be persisted locally and synced to other devices via p2p. It should be doable, similar to screen sharing in etherpad but i have not yet hashed out a complete solution.
Re: Ask HN: What type of Auth are you using on your side projects?
#67I’ve been using https://clerk.com . Not needing to build authentication / the UI / … as well as not worrying about hosting it myself has been nice.
I know the clerk folks a bit. They have a nice generous free tier ( https://clerk.com/pricing ). I believe they don't fully support OAuth/OIDC, which may or may not be a problem based on what you are trying to solve. Any particular strengths or challenges of their approach that you've found?
We do now support this, as of late august! https://clerk.com/changelog/2024-08-20-custom-oauth-provider...
Re: Ask HN: What type of Auth are you using on your side projects?
#68I'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…
Lock in is definitely a valid concern, I emailed customer support and they replied with this: 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 ou…
Head of support at Clerk here, can confirm this is accurate. We're right at the finish line with a project that will give you a secure export of your full user data through the dashboard without needing to email support as well.
We are very committed internally to making sure that folks using Clerk are doing so because they want to be, not because we have made it difficult to leave.
Re: Ask HN: What type of Auth are you using on your side projects?
#69I'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…
Lock in is definitely a valid concern, I emailed customer support and they replied with this: 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 ou…
What's the use case for the encrypted passwords out of curiosity ?
Re: Ask HN: What type of Auth are you using on your side projects?
#70Earlier quoted context omitted.
Lock in is definitely a valid concern, I emailed customer support and they replied with this: 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 ou…
Head of support at Clerk here, can confirm this is accurate. We're right at the finish line with a project that will give you a secure export of your full user data through the dashboard without needing to email support as well. We are very committed internally to making sure that folks using Clerk are doing so because they want to be, not because we have made it difficult to leave.
Amazing initiative! After hearing this I'm definitely keen to try out Clerk for my next project