Need advice about which tool to choose?Ask the StackShare community!
DailyCred vs Spring Security: What are the differences?
Developers describe DailyCred as "Everything you need to manage users for your website or app". Everything you need is included: email verification, password resets, session cookies, and all the UI you need for sign in, and sign up. Skip all this work and get running instantly. If you already have a sign-in system, DailyCred sits side-by-side with the full power of user APIs and dashboards. On the other hand, Spring Security is detailed 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.
DailyCred and Spring Security belong to "User Management and Authentication" category of the tech stack.
Some of the features offered by DailyCred are:
- One API for 12 OAuth Providers- Regardless of how your users sign up, DailyCred gives you access to identity information with a single consistent API. Sometimes users forget exactly how they signed up, so DailyCred prevents duplicate accounts for the same user.
- Security- Use our sign in UI, and get secure authentication over https for free. Don't waste another moment buying or implementing ssl certs ($70 on GoDaddy). Credentials are stored as salted hashes using bcrypt, the industry standard designed by Niels Provos and David Mazieres. DailyCred is securely hosted by Amazon AWS.
- CRM & Backoffice without the Hassle- We create a record of every user and lead that signs up on your website. We even show you how they found you, what campaign they came from, and what they did on your site before signing up. Resetting passwords, monitoring events, banning users, deleting or creating accounts and viewing your website as your users can be handled by any team member.
On the other hand, Spring Security provides the following key features:
- Comprehensive
- Servlet API integration
- Protection against attacks
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.
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/)
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.
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.
Pros of DailyCred
Pros of Spring Security
- Easy to use3
- Java integration3
