Need advice about which tool to choose?Ask the StackShare community!
Spring Security vs Mobile Connect: 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, Mobile Connect is detailed as "Make authentication secure and convenient without usernames or passwords". It is a new authentication service based on the Open ID Connect Standard and SIM cards. Its API offers a secure and convenient method to login to your service.
Spring Security can be classified as a tool in the "Security" category, while Mobile Connect is grouped under "User Management and Authentication".
Some of the features offered by Spring Security are:
- Comprehensive
- Servlet API integration
- Protection against attacks
On the other hand, Mobile Connect provides the following key features:
- Simple, secure authentication
- Free to try, easy to use
- Access a growing user base
Spring Security is an open source tool with 4.08K GitHub stars and 3.49K GitHub forks. Here's a link to Spring Security's open source repository on GitHub.
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 Mobile Connect
Pros of Spring Security
- Easy to use3
- Java integration3
