Marcus Christie created AIRAVATA-2935:
-----------------------------------------
Summary: Long term support version of Keycloak?
Key: AIRAVATA-2935
URL: https://issues.apache.org/jira/browse/AIRAVATA-2935
Project: Airavata
Issue Type: Improvement
Components: Keycloak Authentication
Reporter: Marcus Christie
Investigate what is the best way to keep up to date with Keycloak releases. We
probably don't want to just update to the latest Keycloak release since [they
say on their support page|https://www.keycloak.org/support.html]:
{quote}
The RH-SSO product derives from a specific version of the Keycloak community
and is maintained, patched, and supported by Red Hat commercially for as long
as the terms of your support contract. *The Keycloak community project, on the
other hand, is never patched.* There are no point releases of the community
project and *each release may break backward compatibility*. New features are
developed, experimented with, and baked in community then brought down to be
supported in product if they are popular enough in community. *Think of
Keycloak as bleeding edge with quick releases, unpatched, and limited community
support*, while RH-SSO is stable, supported for a long time, and patched as
bugs and security vulnerabilities are found.
{quote}
(emphasis mine)
I wonder if there is something for RH-SSO like what Centos is to RH Enterprise
Linux? It would be good to research our options.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
