Need advice about which tool to choose?Ask the StackShare community!
Keycloak vs SimpleSAMLphp: What are the differences?
Key Differences between Keycloak and SimpleSAMLphp
Keycloak and SimpleSAMLphp are both open-source identity and access management solutions, but there are several key differences between them:
Authentication methods: Keycloak supports a wide range of authentication methods, including social login, multi-factor authentication, and passwordless authentication. On the other hand, SimpleSAMLphp mainly focuses on traditional username/password authentication and SAML-based federation.
Support for protocols: Keycloak supports multiple protocols such as SAML, OpenID Connect, OAuth, and more. SimpleSAMLphp, as the name suggests, primarily focuses on SAML protocol for identity federation. It provides extensive support for SAML features and profiles.
User management: Keycloak provides a comprehensive user management interface with support for user self-registration, password reset, and user roles/permissions. SimpleSAMLphp has limited built-in user management capabilities and usually relies on external user management systems or identity providers.
Integration with external systems: Keycloak offers out-of-the-box integration with various external systems like LDAP, Active Directory, and databases. SimpleSAMLphp also supports integration with external systems but requires more manual configuration and customization.
Extensibility and customization: Keycloak provides a highly extensible platform where developers can customize its behavior and add new features using Java APIs and extensions. SimpleSAMLphp offers customization options through PHP programming, but it may require more effort and expertise compared to Keycloak.
Community and support: Keycloak has a vibrant community of users and developers, backed by the Red Hat organization. It offers professional support and regular updates. SimpleSAMLphp also has an active community, but it may be relatively smaller and have limited support options.
In summary, Keycloak provides a more comprehensive and versatile solution with support for a wide range of authentication methods, protocols, and integrations, along with extensive customization options. SimpleSAMLphp, on the other hand, is a specialized solution primarily focused on SAML-based federation and may be a suitable choice for organizations with specific SAML requirements.
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 Keycloak
- It's a open source solution33
- Supports multiple identity provider24
- OpenID and SAML support17
- Easy customisation12
- JSON web token10
- Maintained by devs at Redhat6
Pros of SimpleSAMLphp
Sign up to add or upvote prosMake informed product decisions
Cons of Keycloak
- Okta7
- Poor client side documentation6
- Lack of Code examples for client side5