Upgrade to Keycloak 4.2.0.Final
See original GitHub issueKeycloak 4.0.0.Final has been released and there also a starter available for Spring Boot 2. I can provide a PR if needed , what I did locally in the application.yml :
mappings:
- versionRange: 2.0.0.RELEASE
groupId: org.keycloak
artifactId: keycloak-spring-boot-2-starter
- versionRange: "[1.5.3.RELEASE,2.0.0.M1)"
groupId: org.keycloak
artifactId: keycloak-spring-boot-starter
And the new Keycloak version is updated in the bom section of the yaml file.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Release Notes - Keycloak
Upgrade to Wildfly 26.0.0. Keycloak server was upgraded to use Wildfly 26.0.0.Final as the underlying container. For more information on WildFly ...
Read more >[keycloak-user] Upgrade to 4.2.0 fails
Previous message: [keycloak-user] Upgrade to 4.2.0 fails; Next message: [keycloak-user] Secure CORS ... Final release, which fixes this.
Read more >keycloak-services » 4.2.0.Final - Maven Repository
Keycloak REST Services » 4.2.0.Final ; License, Apache 2.0 ; Tags, keycloakservice ; Date, Aug 01, 2018 ; Files, jar (1.9 MB) View...
Read more >Untitled
4.0.0 org.jboss jboss-parent 19 Keycloak Keycloak SSO org.keycloak ... 20.0 9.1.0.v20131115 3.4.1 5.1.29 4.2.0 7.1.0 9.3-1100-jdbc41 1.3.7 1.0.2.Final 4.0.4 ...
Read more >Upgrading to Paragon Insights Release 4.X - TechLibrary
Identify the keycloak pod in the namespace. · Connect to the keycloak pod. · Run the following command to generate the backup file:...
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
@sebastienblanc nah, we’re good. Let’s switch to Keycloak 4.1 then, thanks!
@snicoll KC 4.2 has just been released, is available on Maven Central and solves the BOM issues.