2 ms·
It is more and more common to have frameworks include blueprints for login pages, but it used not to be the case at all. I wouldn't say that it's that common no
by baby 8y ago
It is more and more common to have frameworks include blueprints for login pages, but it used not to be the case at all. I wouldn't say that it's that common nowadays either.
- scarface74 8y agoMost frameworks have an easy way to offload user authentication to third parties like Facebook, Amazon, Twitter, Google, etc. I would trust any of them to get it “right” before I would trust most developers. If you need authentication for an internal corporate app, there is always authentication with the corporate directory services or something like Okta.
- majewsky 8y agoSecurity doesn't exist in a vacuum. It's only one of multiple concerns. For instance: > offload user authentication to third parties like Facebook, Amazon, Twitter, Google, etc. Have fun getting that through the GDPR compliance audit.
- flukus 8y agoIME these usually have shortcomings that the business won't accept, a few I've come across: 1. Only AD or only database accounts when you need a combination of both, 2. Only offering role based security when you need something more granular. Side note - a lot of managers expect to be able to jest drop this in a a late requirement, but it usually requires significant work. 3. Not offering documentation on integration. If it includes a permissions system for instance then I also need a way to join against a table of granted permissions for performance. 4. Providing their own UI that's hard to get around. Great for a PoC but often harder to integrate with the rest of the system than writing the login page from scratch. Generally I try to use an existing authentication system but have often had to create a custom security framework.