Currently, Passport.js repo has 324 open issues, and Jared (the original author) seems to be the one doing most of the work. Also, given that the documentation is not proper. Is it worth using Passport.js?
As of now, StackShare shows it has 29 companies using it. How do you implement auth in your project or your company? Are there any good alternatives to Passport.js? Should I implement auth from scratch?
Hey all, We're currently weighing up the pros & cons of using Firebase Authentication vs something more OTB like Auth0 or Okta to manage end-user access management for a consumer digital content product. From what I understand so far, Something like Firebase Auth would require more dev effort but is likely to cost less overall, whereas OTB, you have a UI-based console which makes config by non-technical business users easier to manage. Does anyone else have any intuitions or experiences they could share on this, please? Thank you!
I started our team on Amazon Cognito because I was a Solutions Architect at AWS and found it really easy to follow the tutorials and get a basic app up and running with it.
When our team started working with it, they very quickly became frustrated because of the poor documentation. After 4 days of trying to get all the basic passwordless auth working, our lead engineer made the decision to abandon it and try Auth0... and managed to get everything implemented in 4 hours.
The consensus was that Cognito just isn't mature enough or well-documented, and that the implementation does not cater for real world use cases the way that it should. I believe Amplify has made some of this simpler, but I would still recommend Auth0 as it's been bulletproof for us, and is a sensible price.
Stormpath is an authentication and user management service that helps development teams quickly and securely build web and mobile applications and services.
A set of unified APIs and tools that instantly enables Single Sign On and user management to all your applications.
You can create unique identities for your users through a number of public login providers (Amazon, Facebook, and Google) and also support unauthenticated guests. You can save app data locally on users’ devices allowing your applications to work even when the devices are offline.
User Authentication as a Service;
Authorization – Easily model and manage your data, including pre-built roles;
Flexible User Profiles;
Single Sign-On Across your Apps;
Easy Partitioning for Multi-Tenant SaaS;
Pre-built Security Workflows - Password Reset, Email Verification;
Hosted Login Portal;
Social Login;
API Authentication & Key Management;
Token-based Authentication;
Multi-Factor Authentication;
Active Directory & LDAP Integrations;
Advanced Password Security;
Admin Console;
Safe Harbor Compliance;
HIPAA Compliance;
Private Deployments;
User and Password support with verification and forgot password email workflow; Painless SAML Auth with Enterprises; Integration with 20+ Social Providers; SDKs for all platforms mobile and web; Token-based authentication for APIs
Manage Unique Identities;Work Offline;Store and Sync across Devices;Seamless Guest Access;Safeguard AWS Credentials;Control Access to AWS Resources
Statistics
Stacks
40
Stacks
1.3K
Stacks
624
Followers
96
Followers
2.1K
Followers
917
Votes
146
Votes
215
Votes
34
Pros & Cons
Pros
29
Authentication
22
User Management
19
API Authentication
17
Security Workflows
17
Token Authentication
Cons
4
Discontinued
Pros
70
JSON web token
31
Integration with 20+ Social Providers
20
It's a universal solution
20
SDKs
15
Amazing Documentation
Cons
15
Pricing too high (Developer Pro)
7
Poor support
4
Status page not reflect actual status
4
Rapidly changing API
Pros
14
Backed by Amazon
7
Manage Unique Identities
4
Work Offline
3
MFA
2
Store and Sync
Cons
4
Massive Pain to get working
3
Documentation often out of date
2
Login-UI sparsely customizable (e.g. no translation)