Keycloak

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.

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. This followed a merging of the PicketLink codebase into Keycloak.

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. 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.

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

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.

• OpenAM
• List of single sign-on implementations