tickets #101993
openEnable keycloak for s390x
0%
Description
Keycloak is a SSO solution for container platforms.
Somebody did first steps with buildings for x86:
https://build.opensuse.org/package/show/home:fstrba/keycloak
ToDos:
1) Enable keycloak for s390x and test it
2) Change the base application server to Tomcat if not workable (optional)
3) Ask on opensuse-factory list for the correct branch to publish
4) Submit to the upstream branch
Keycloak download page: https://www.keycloak.org/downloads
Updated by AdaLovelace over 2 years ago
Keycloak-x has been (pre-)released. It will be using Quarkus instead of WildFly in the future.
Therefore, we will build and test it with the new development version based on Quarkus.
Updated by AdaLovelace about 2 years ago
Nice news today about possible Red Hat support for keycloak/RH SSO on the foundation of other Linux distributions.
Red Hat is providing support subscriptions for keycloak (Red Hat SSO), so long as the "supported configuration" is matching:
https://access.redhat.com/articles/2342861
You can use every rpm based Linux distribution (therefore also (open)SUSE :)).
What is included in the supported version? They accept also self-built container images. Here are the existing supported Dockerfiles we can use as a foundation with openSUSE:
1) https://catalog.redhat.com/software/containers/rh-sso-7/sso74-openj9-openshift-rhel8/5e7e0430bed8bd66f8390b4e?container-tabs=dockerfile
2) https://catalog.redhat.com/software/containers/rh-sso-7/sso74-openshift-rhel8/5e7e033d5a1346687697bbd3?container-tabs=dockerfile
Therefore, we should use OpenJDK 1.8, 11 together with keycloak for a compatibility with Enterprise support.
Afterwards, they are providing support the the application in the container, but not for the operating system.
Updated by AdaLovelace about 2 years ago
Updated by AdaLovelace about 2 years ago
You are allowed to update the tar archive.
Use following commands for that in the replacement:
1) osc rm old_archive.tar.gz
3) Download new archive ownload page
4) osc add new_archive.tar.gz
6) update keycloak.spec with new version numbers
7) osc ci
8) If builds are failing, look, whether used patches are required (test it with removing ones)
Updated by hrauch almost 2 years ago
- Status changed from New to In Progress
- Assignee set to hrauch