3 ms·
What are people using for auth these days?
by davidw 3y ago
What are people using for auth these days?
- jossclimb 3y agoI implemented it myself in Go using github.com/golang/oauth2 and github.com/golang-jwt/jwt.
- davidw 3y agoThe article mentions "Auth services, obviously". I'm curious, because to me it seems like people have mostly used open source things they include in their apps.
- deleted 3y ago[deleted]
- AntonCTO 3y agoKeycloak is good for most use cases. I heard that some teams failed with Cognito (AWS). But for the current product I built my own server. I was tired of fighting some Keycloak specifics like - No "stay logged in forever if you use the (web) application from time to time". - Bugs around caching (especially in integration tests). - No zero downtime deployment (should be fixed soon, too late for me) - Weaknesses around configuration. I used to use keycloak-config-cli, which is good enough for most use cases. And some missing functionality that needs to be implemented very often, like "Accept ToS before profile is created". Having said that, Keycloak is a very good product and I haven't found a better free and open source product. But sometimes it is not the right choice. By the way, I personally don't plan to outsource user data and credentials to a 3rd party service. Although Auth0 is very sexy.
- tmountain 3y agoPocketBase, Supabase, Firebase… all your base are belong to auth.