Keycloak
| Developer(s) | WildFly, a division of Red Hat |
|---|---|
| Initial release | 10 September 2014 |
| Stable release | 24.0.3
/ 16 April 2024[1] |
| Repository | |
| Written in | Java |
| Type | Single sign-on system |
| License | Apache License 2.0 |
| Website | www |
Keycloak is an open source software product to allow single sign-on with identity and access management aimed at modern applications and services. As of March 2018[update] this WildFly community project is under the stewardship of Red Hat who use it as the upstream project for their Red Hat build of Keycloak.
Keycloak supports various protocols such as OpenID, OAuth version 2.0 and SAML and provides features such as user management, two-factor authentication, permissions and roles management, creating token services, etc.[2]
History[edit]
The first production release of Keycloak was in September 2014, with development having started about a year earlier. In 2016, Red Hat switched the RH SSO product from being based on the PicketLink framework to being based on the Keycloak upstream Project.[3] This followed a merging of the PicketLink codebase into Keycloak.[4][5]
To some extent Keycloak can now also be considered a replacement of the Red Hat JBoss SSO open source product which was previously superseded by PicketLink.[6][7] As of March 2018[update], JBoss.org is redirecting the old jbosssso subsite to the Keycloak website. The JBoss name is a registered trademark and Red Hat moved its upstream open source projects names to avoid using JBoss, JBoss AS to Wildfly being a more commonly recognized example.[8]
Features[edit]
The features of Keycloak include:
- User registration
- Social login
- Single sign-on/sign-off across all applications belonging to the same realm
- Two-factor authentication
- LDAP integration
- Kerberos broker
- Multitenancy with per-realm customizable skin
- Custom extensions to extend the core functionality
- The ability to use it on-premise or use a cloud service provider
- Central administration management
- Plugin-based architecture
- The ability to assign users to specific roles and subgroups and restrict access of certain individuals to parts of the application[9]
Components[edit]
There are two main components of Keycloak:
- Keycloak server, including the API and graphical interface.
- Keycloak application adapter: a set of libraries to call the server.[10]
See also[edit]
References[edit]
- ^ "Keycloak 24.0.3 released". 16 April 2024. Retrieved 16 April 2024.
- ^ "Open Source Identity and Access Management". keycloak. Retrieved 2024-01-23.
- ^ Atkisson, Brian (4 October 2016). "How Red Hat re-designed its Single Sign On (SSO) architecture, and why". Red Hat. Archived from the original on 9 January 2018. Retrieved 7 March 2018.
- ^ Dawidowicz, Boleslaw (10 March 2015). "PicketLink and Keycloak projects are merging!". PicketLink.org. Archived from the original on 11 September 2015. Retrieved 7 March 2018.
- ^ Peeples, Kenneth (28 May 2014). "What is the difference between Picketlink and Keycloak?". JBossDeveloper. Archived from the original on 5 April 2017. Retrieved 7 March 2018.
- ^ "JBosssso (archived) Website". Archived from the original on 30 May 2014.
- ^ Kalali, Masoud (30 May 2010). GlassFish Security. PACKT. p. 182. ISBN 978-1-847199-38-6.
- ^ "Load Balancing Wildfly and JBoss Application Servers with NGINX Open Source and NGINX Plus | NGINX Documentation". docs.nginx.com. Retrieved 2023-10-11.
- ^ "Keycloak". www.keycloak.org. Retrieved 2024-03-25.
- ^ "Securing Applications and Services Guide".
External links[edit]
- Official website
- Sébastien Blanc (June 16, 2017). "Easily Secure Your Spring Boot Applications With Keycloak". dzone.com.
- Free Keycloak tutorials
- "Writing Keycloak extensions: Key concepts and anti-patterns". zone2.tech. November 24, 2022.
 | This security software article is a stub. You can help Wikipedia by expanding it. |