I like to use .NET Core Identity services with Azure AD B2C. Very easy to setup and generic interfaces are already defined for password reset, etc.
https://docs.microsoft.com/en-us/aspnet/core/security/authen...
Show HN: Clerk – all of user management as-a-service, not just authentication
41–50 of 234 posts
Re: Show HN: Clerk – all of user management as-a-service, not just authentication
#42Earlier quoted context omitted.
This is my question as well. It's an honest question and hopefully someone can educate me. Why would anyone trust a third party with what is the most important asset, their users? Thank you in advance.
I can answer with the opposite question. Why would you trust your homemade solution instead of heavily invested experts? Auth0 (and Okta and a thousand others) do nothing but auth and customer management and do it at 1000X the scale as most enterprises. They do it way better than your IT team could possibly do it. And support every cutting edge feature and potential use case. You can also get them to absorb indemnity…
Authentication is webdev 101. If you can't roll your own you're in the wrong industry.
I really can't think of any good reason to hand crucial control of a site over to any third party, much less user authentication where one breach will potentially cost you millions and land you in jail.
The whole business model seems to revolve around being a crutch for people not capable or competent of running their own services.
Re: Show HN: Clerk – all of user management as-a-service, not just authentication
#43Is this hosted on your own backend? Should the time or need arise if available, what are some recommended steps to migrate off if needed?
Re: Show HN: Clerk – all of user management as-a-service, not just authentication
#44Earlier quoted context omitted.
Downvoted? Why? When user-related information is outsourced, the GDPR is absolutely relevant. Even the Google(!) screenshot on the landing page shows "Privacy and personalization" as the first item, that goes to show...
Braden, one of the founders, I gave you an upvote! GDPR is definitely at the top of our mind. We would love to make it so developers don't need to think about, or make it easy to think about, GDPR and CCPA, and any future regulations that come up.
The question becomes; where is your company incorporated, where are your servers located. I was looking around on your website and it's very light on such details.
Re: Show HN: Clerk – all of user management as-a-service, not just authentication
#45As someone who uses Django which has user management out of the box, why would I use a service like this?
Common use case is when you multiple apps that all require the same auth infrastructure. IE a suite of apps for a business.
Re: Show HN: Clerk – all of user management as-a-service, not just authentication
#46Earlier quoted context omitted.
This is my question as well. It's an honest question and hopefully someone can educate me. Why would anyone trust a third party with what is the most important asset, their users? Thank you in advance.
Hey, Braden one of the founders. It's a good question, and a question that gets asked a lot. Out of curiosity would you trust a more established company like Auth0 or Firebase? We hope to gain developers trust over time, and we want to build a tool that makes it dramatically easier to build out session management, and a lot of these user flows. A similar question that was asked only a few (10?) years ago, was "why wo…
> would you trust a more established company like Auth0 or Firebase?
Auth0 maybe. Firebase is created by an advertising agency, so no.
Re: Show HN: Clerk – all of user management as-a-service, not just authentication
#47Earlier quoted context omitted.
I can answer with the opposite question. Why would you trust your homemade solution instead of heavily invested experts? Auth0 (and Okta and a thousand others) do nothing but auth and customer management and do it at 1000X the scale as most enterprises. They do it way better than your IT team could possibly do it. And support every cutting edge feature and potential use case. You can also get them to absorb indemnity…
Authentication is webdev 101. If you can't roll your own you're in the wrong industry. I really can't think of any good reason to hand crucial control of a site over to any third party, much less user authentication where one breach will potentially cost you millions and land you in jail. The whole business model seems to revolve around being a crutch for people not capable or competent of running their own services.
Well, if you look at how many sites break auth, or something in the login flow... This is clearly not the case for most companies. Auth is definitely simpler than most problems, but plenty of teams get it wrong.
Re: Show HN: Clerk – all of user management as-a-service, not just authentication
#48Really good stuff. The Next.js integration story is already really quite good[1] and the Clerk team has really good ideas on how to make it even better and more seamless. It's great to see a service focus on taking away all the pain related to user management, not just login. [1] https://frontend-docs.clerk.dev/react/quick-starts/next.js
It looks great!
Re: Show HN: Clerk – all of user management as-a-service, not just authentication
#49Are the components only available for React?