3 ms·
The sweet spot is using some well known library. A classic in the Rails world is Devise. There is usually one for any language or framework.
by pmontra 6y ago
The sweet spot is using some well known library. A classic in the Rails world is Devise. There is usually one for any language or framework.
- robotdan 6y agoYes, this is an excellent choice as long as all of yours apps live in the Ruby world.
- pmontra 6y agoActually I built a single sign on system for a Rails app and a WordPress site many years ago, based on Devise and probably (can't remember) some PHP code on WP. Probably also a Rails+phpBB SSO. They were meant to be short lived services and luckily they did. The reason is that in a mixed language / framework environment it's better to have some centralized authentication and authorization service and a standard API to access it. Having to write and maintain N adapters is going to take a toll on the development team. However I never self hosted a service like that so I don't want to give any suggestions about what to use.
- hashmymustache 6y agoIs there a good one that integrates with Express?
- victorbojica 6y agoPassport. It provides a lot of authentication schemes
- bradyd 6y agoPassport is an Express middleware for authentication. It supports pluggable "strategies" for supporting different types of authentication, from basic username/password to OAuth and many others. https://www.npmjs.com/package/passport https://www.npmjs.com/package/passport
- _0o6v 6y agoA sweet spot only is as much as the code is already written, but there's a huge amount of ops and security work that goes into rolling your own auth. For 99.9% of businesses, don't roll your own auth. Just don't do it. Use an auth service.