Keycloak vs Stormpath

Overview

Stormpath

Stacks40

Followers96

Votes146

Keycloak

Stacks780

Followers1.3K

Votes102

Keycloak vs Stormpath: What are the differences?

Token Management: Keycloak offers robust token management capabilities, allowing for fine-grained control over access tokens, refresh tokens, and ID tokens. On the other hand, Stormpath provides more limited token management features, focusing primarily on authentication and authorization.
User Federation: Keycloak supports user federation, enabling organizations to integrate with multiple external identity providers and directories easily. In contrast, Stormpath lacks native support for user federation and relies on its internal user store for authentication and authorization.
Customization: Keycloak provides extensive customization options, allowing developers to tailor the authentication and authorization workflows to meet specific business requirements. Stormpath, while offering some customization features, has limitations compared to the flexibility provided by Keycloak.
Scalability: Keycloak is designed for scalability, capable of handling large numbers of users and high volumes of authentication requests efficiently. Stormpath, while suitable for small to medium-sized applications, may face challenges in scaling to support enterprise-level workloads effectively.
Integration Ecosystem: Keycloak has a vast integration ecosystem with support for various platforms, protocols, and programming languages, making it versatile for diverse application environments. Stormpath, while versatile in integration capabilities, may have fewer options compared to Keycloak's extensive ecosystem.
Community Support: Keycloak benefits from a large and active community that contributes to its development, provides support, and offers a wide range of resources for users. Stormpath, on the other hand, has a smaller community base, which may impact the availability of resources and support for users.

In Summary, Keycloak and Stormpath differ in terms of token management, user federation, customization options, scalability, integration ecosystem, and community support.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on Stormpath, Keycloak

sindhujasrivastava

Jan 16, 2020

Needs advice

I am working on building a platform in my company that will provide a single sign on to all of the internal products to the customer. To do that we need to build an Authorisation server to comply with the OIDC protocol. Earlier we had built the Auth server using the Spring Security OAuth project but since in Spring Security 5.x it is no longer supported we are planning to get over with it as well. Below are the 2 options that I was considering to replace the Spring Auth Server.

Keycloak
Okta
Auth0 Please advise which one to use.

258k views258k

Comments

Detailed Comparison

Stormpath	Keycloak
Stormpath is an authentication and user management service that helps development teams quickly and securely build web and mobile applications and services.	It is an Open Source Identity and Access Management For Modern Applications and Services. It adds authentication to applications and secure services with minimum fuss. No need to deal with storing users or authenticating users. It's all available out of the box.
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;	-
Statistics
Stacks 40	Stacks 780
Followers 96	Followers 1.3K
Votes 146	Votes 102
Pros & Cons
Pros 29 Authentication 22 User Management 19 API Authentication 17 Token Authentication 17 Security Workflows Cons 4 Discontinued	Pros 33 It's a open source solution 24 Supports multiple identity provider 17 OpenID and SAML support 12 Easy customisation 10 JSON web token Cons 7 Okta 6 Poor client side documentation 5 Lack of Code examples for client side
Integrations
Node.js G Suite Spring Framework Facebook Spring Ruby Java AngularJS JavaScript Django	No integrations available

What are some alternatives to Stormpath, Keycloak?

Auth0

A set of unified APIs and tools that instantly enables Single Sign On and user management to all your applications.

Devise

Devise is a flexible authentication solution for Rails based on Warden

Firebase Authentication

It provides backend services, easy-to-use SDKs, and ready-made UI libraries to authenticate users to your app. It supports authentication using passwords, phone numbers, popular federated identity providers like Google,

Amazon Cognito

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.

WorkOS

Start selling to enterprise customers with just a few lines of code.

OAuth.io

OAuth is a protocol that aimed to provide a single secure recipe to manage authorizations. It is now used by almost every web application. However, 30+ different implementations coexist. OAuth.io fixes this massive problem by acting as a universal adapter, thanks to a robust API. With OAuth.io integrating OAuth takes minutes instead of hours or days.

OmniAuth

OmniAuth is a Ruby authentication framework aimed to abstract away the difficulties of working with various types of authentication providers. It is meant to be hooked up to just about any system, from social networks to enterprise systems to simple username and password authentication.

ORY Hydra

It is a self-managed server that secures access to your applications and APIs with OAuth 2.0 and OpenID Connect. It is OpenID Connect Certified and optimized for latency, high throughput, and low resource consumption.

Kinde

Simple, powerful authentication that you can integrate in minutes. Free your users from passwords with secure and frictionless one click sign up and sign in. Built from the ground up using the best in class security protocols available today.

Satellizer

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.

Related Comparisons

Keycloak vs Stormpath: What are the differences?

Token Management: Keycloak offers robust token management capabilities, allowing for fine-grained control over access tokens, refresh tokens, and ID tokens. On the other hand, Stormpath provides more limited token management features, focusing primarily on authentication and authorization.
User Federation: Keycloak supports user federation, enabling organizations to integrate with multiple external identity providers and directories easily. In contrast, Stormpath lacks native support for user federation and relies on its internal user store for authentication and authorization.
Customization: Keycloak provides extensive customization options, allowing developers to tailor the authentication and authorization workflows to meet specific business requirements. Stormpath, while offering some customization features, has limitations compared to the flexibility provided by Keycloak.
Scalability: Keycloak is designed for scalability, capable of handling large numbers of users and high volumes of authentication requests efficiently. Stormpath, while suitable for small to medium-sized applications, may face challenges in scaling to support enterprise-level workloads effectively.
Integration Ecosystem: Keycloak has a vast integration ecosystem with support for various platforms, protocols, and programming languages, making it versatile for diverse application environments. Stormpath, while versatile in integration capabilities, may have fewer options compared to Keycloak's extensive ecosystem.
Community Support: Keycloak benefits from a large and active community that contributes to its development, provides support, and offers a wide range of resources for users. Stormpath, on the other hand, has a smaller community base, which may impact the availability of resources and support for users.

In Summary, Keycloak and Stormpath differ in terms of token management, user federation, customization options, scalability, integration ecosystem, and community support.

Keycloak vs Stormpath

Overview