Am I the only developer who prefers building authentication myself instead of relying heavily on third-party auth libraries?

3 replies 36 views

Am I the only developer who prefers building authentication myself instead of relying heavily on third-party auth libraries? I like having control over how authentication works in my application. What happens if the library has a breaking change, gets abandoned, or develops a serious issue in the future? I’m not saying third-party auth is bad. It can save time and be very useful. But for me, understanding and controlling the authentication flow feels more reliable. What’s your preference: custom authentication or third-party authentication? And why?

View passport

React

Replies

3 replies

@abdulfatai Builder 1 week ago

What’s your preference: custom authentication or third-party authentication? And why?

React

Permalink

@james 1 week ago

I get the appeal of having full control, but auth is one of those areas where I’d rather not reinvent the wheel. Third-party solutions can save a lot of time, especially when security is involved, but understanding what’s happening is still important.

React

Permalink

@abdulfatai Builder 1 week ago

I agree that third-party solutions can save time, especially when security is involved. My concern is more about long-term control and dependency. If a library introduces breaking changes, gets abandoned, or has issues that affect my application, I want to understand how to handle them. I believe the best approach is to understand authentication deeply, whether you build it yourself or use a third-party solution.

React

Permalink