Upgrade to Keycloak 7
See original GitHub issueWe are now two major versions behind. We should upgrade to Keycloak 6. What needs to be done to accomplish this:
- Upgrade the keycloak version in the parent
pom.xml
- Upgrade the
apicurio-studio-auth
docker image to use KC 6 - Make sure the Apicurio login theme works with KC 6 and update accordingly
- Make sure that https://github.com/Apicurio/apicurio-keycloak-extensions works with KC 6
- TEST TEST TEST - especially identity providers (github, gitlab, bbucket)
Issue Analytics
- State:
- Created 4 years ago
- Comments:14 (7 by maintainers)
Top Results From Across the Web
Upgrading Guide - Keycloak
This guide describes how to upgrade Keycloak. It is recommended that you start by upgrading the Keycloak server first and Keycloak adapters ...
Read more >Migration from older versions | keycloak-documentation
To upgrade to a new version of Keycloak first download and install the new version of Keycloak. Once the new version is installed...
Read more >Upgrading Notes - Bitnami Documentation
Keycloak packaged by Bitnami for Kubernetes ... To upgrade to 7.0.0 from 6.x, it should be done reusing the PVC(s) used to hold...
Read more >Upgrading Guide Red Hat Single Sign-On 7.5
Red Hat Single Sign-On (RH-SSO) 7.5 is based on the Keycloak project and provides ... upgrade from Red Hat Single Sign-On 7.x to...
Read more >Upgrading Keycloak from 11 to 20 (Docker) - Getting advice
fouringiz December 7, 2022, 9:46pm #1. Hello community planning to upgrade keycloak from 11 to 20 (docker) considering WildFly to Quarkus migration, ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Just a heads up, might make the testing steps a bit easier on you.
I’m currently running Apicurio in a Docker cluster using Keycloak 7.0. The current realm template file works and imports without issue. Integration with a local Gitlab instance also works following the instructions in the docs.
Only major change was the ENV variables for keycloak itself to reach it’s DB. The Keycloak settings look a bit different (there are more of them), but the important ones are present and the same.
I’m not using the Apicurio themed Keycloak, so can’t speak for that.
I’ll try to get studio.apicur.io updated to use KC 7 asap, but I’m guessing no one really cares. 😃