Repository navigation
Differences, if any, between Keycloak from the community and from Redhat ? #52252
Replies: 1 comment
|
The Red Hat build is a downstream product made from selected upstream Keycloak releases, rather than a separate SSO implementation. Its configuration and admin concepts are largely familiar, but a community release and a Red Hat product release should not be treated as interchangeable version-for-version. Upstream Keycloak is Apache-licensed, receives new features first, and follows the community release cadence. Support comes from the project and its community. Red Hat’s build adds a supported distribution, a defined product lifecycle, and a narrower tested matrix of JDKs, databases and deployment platforms. Red Hat can also backport security and important fixes to a maintained product release. Preview features and third-party extensions may still run there, but that does not automatically make them part of the supported configuration. For a lab, a self-supported service, or early access to current features, the community build is usually the direct choice. If the requirement is a support SLA, a certified configuration, or predictable maintenance windows, use the Red Hat build and check its supported configurations and product lifecycle before choosing a version. A setup that works upstream is not necessarily one Red Hat will support. |
Uh oh!
There was an error while loading. Please reload this page.
Hello everyone,
Is there any difference between Keycloak, community build I would say vs Keycloak Redhat build ?
Best Regards.
All reactions