Need advice about which tool to choose?Ask the StackShare community!
Keycloak vs Stormpath: What are the differences?
Developers describe Keycloak as "An open source identity and access management solution". 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. On the other hand, Stormpath is detailed as "User Management and Authentication for Developers". Stormpath is an authentication and user management service that helps development teams quickly and securely build web and mobile applications and services.
Keycloak and Stormpath can be primarily classified as "User Management and Authentication" tools.
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. 1. Keycloak 2. Okta 3. Auth0 Please advise which one to use.
It isn't clear if beside the AuthZ requirement you had others, but given the scenario you described my suggestion would for you to go with Keycloak. First of all because you have already an onpremise IdP and with Keycloak you could maintain that setup (if privacy is a concern). Another important point is configuration and customization: I would assume with Spring OAuth you might have had some custom logic around authentication, this can be easily reconfigured in Keycloak by leveraging SPI (https://www.keycloak.org/docs/latest/server_development/index.html#_auth_spi). Finally AuthZ as a functionality is well developed, based on standard protocols and extensible on Keycloak (https://www.keycloak.org/docs/latest/authorization_services/)
We have good experience using Keycloak for SSO with OIDC with our Spring Boot based applications. It's free, easy to install and configure, extensible - so I recommend it.
You can also use Keycloak as an Identity Broker, which enables you to handle authentication on many different identity providers of your customers. With this setup, you are able to perform authorization tasks centralized.
Pros of Keycloak
- It's a open source solution32
- Supports multiple identity provider23
- OpenID and SAML support15
- Easy customisation10
- JSON web token9
- Maintained by devs at Redhat5
Pros of Stormpath
- User Management22
- API Authentication19
- Token Authentication17
- Security Workflows17
- Easy setup and great support7
- Great customer support7
- they manage the required, so I can focus on innovation6
- Private Deployment3
- Will sign BAA for HIPAA-compliance2
- Rapid Development1
- SAML Support0
Sign up to add or upvote prosMake informed product decisions
Cons of Keycloak
- Poor client side documentation6
- Lack of Code examples for client side5
Cons of Stormpath