Need advice about which tool to choose?Ask the StackShare community!
Spring Security vs Stormpath: What are the differences?
Developers describe Spring Security as "A powerful and highly customizable authentication and access-control framework". It is a framework that focuses on providing both authentication and authorization to Java applications. The real power of Spring Security is found in how easily it can be extended to meet custom requirements. 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.
Spring Security and Stormpath belong to "User Management and Authentication" category of the tech stack.
Some of the features offered by Spring Security are:
- Comprehensive
- Servlet API integration
- Protection against attacks
On the other hand, Stormpath provides the following key features:
- User Authentication as a Service
- Authorization – Easily model and manage your data, including pre-built roles
- Flexible User Profiles
Spring Security is an open source tool with 3.63K GitHub stars and 3.2K GitHub forks. Here's a link to Spring Security's open source repository on GitHub.
Monkey Exchange, Debut, and Monbanquet.fr are some of the popular companies that use Spring Security, whereas Stormpath is used by Stormpath, Forerunner Games, and Notify-e. Spring Security has a broader approval, being mentioned in 12 company stacks & 9 developers stacks; compared to Stormpath, which is listed in 3 company stacks and 4 developer stacks.
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 Spring Security
- Easy to use3
- Java integration3
Pros of Stormpath
- Authentication29
- User Management22
- API Authentication19
- Token Authentication17
- Security Workflows17
- Secure16
- 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 Spring Security
Cons of Stormpath
- Discontinued4
