The parent project contains a Docker Compose file that fires up a Docker cluster, to simulate a real-life scenario where Keycloak would connect to a remote MS SQL Server database. The example consists of a Maven project with a single module and a sub-module. For the purpose of this example, the database of choice is Microsoft SQL Server Express Edition, but it should be a very similar procedure for any other relational database. On this article is provided a full example of how to properly configure a Keycloak deployment on Docker to use an alternative database - one not supported by the Docker image by default. The reason for that is that the standalone.xml configuration file - where the changes are supposed to be made - is altered at deployment time via some jboss-cli scripts. IntroductionĪlthough Keycloak has some documentation on how to perform Relational Database Setup, this task is much less straight forward when using the official Keycloak Docker image.
This article follows up on “Keycloak as OpenID Connect Provider”. Please ignore that.A working example on how to configure Keycloak to use an alternative database when running on Dockerĭisclaimer: The git repository for this guide can be found here. Yeah, I'll bet it's still complaining to you about Now go open a WildFly 9 standalone.xml (like the one that comes out of the tar in the first place) and see if most of that red crap has turned back to a friendlier, less alarming color. Copy the file above into your project's.
idea/misc.xml file and back it up somewhere just in case.
0 kommentar(er)
