Keratin AuthN vs Satellizer: What are the differences?
Keratin AuthN: Accounts and Auth Microservice in Go. AuthN manages a database of user accounts with sign-in credentials and related attributes. Your application frontend relies on AuthN for creating accounts, logging in, forgotten passwords, and session maintenance; Satellizer: Token-based AngularJS Authentication. Satellizer is a simple to use, end-to-end, token-based authentication module for AngularJS with built-in support for Google, Facebook, LinkedIn, Twitter authentication providers, plus Email and Password sign-in method. You are not limited to the sign-in options above, in fact you can add any OAuth 1.0 or OAuth 2.0 provider by passing provider-specific information during the configuration step.
Keratin AuthN and Satellizer can be primarily classified as "User Management and Authentication" tools.
Keratin AuthN and Satellizer are both open source tools. Satellizer with 8.08K GitHub stars and 1.27K forks on GitHub appears to be more popular than Keratin AuthN with 775 GitHub stars and 45 GitHub forks.
What is Keratin AuthN?
What is Satellizer?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose Keratin AuthN?
What are the cons of using Keratin AuthN?
What are the cons of using Satellizer?
What companies use Keratin AuthN?
Sign up to get full access to all the companiesMake informed product decisions
Great for building Node + Angular authentication workflows. Passport is great, but doesn't have the Angular client-side authentication support, so Satellizer is a better fit.