Starting the Keycloak

If Keycloak is started in a different mode (switching from development mode to production mode or vice versa), an additional step is required. Keycloak X is based on Quarkus and compiles configuration files in advance for faster startup and better performance. This step is called "building" the application. If the step is not done after the configuration changes (e.g., database configuration), the last configuration changes may not be applied.

In the proxy setup described here, Keycloak must be started in production mode, although no certificates and no HTTPS configuration need to be provided. The Keycloak startup scripts included in the X4 BPMS usually start the Keycloak in development mode. If that is the case, you can start Keycloak in production mode using the following options:

To start the Keycloak manually

1. Execute /c:/X4/keycloak/bin/kc.sh build to compile the Keycloak configuration in advance.
2. Execute /c:/X4/keycloak/bin/kc.sh start to start the Keycloak in production mode.

To modify the start scripts

1. Execute /c:/X4/keycloak/bin/kc.sh buildto compile the Keycloak configuration in advance.
2. In /c:/X4/startKeycloak.sh, modify the entry start-dev in start. Now, the Keycloak is started in production mode every time the script is executed.

To modify the daemon configuration file

1. Führen Sie /opt/X4/keycloak/bin/kc.sh buildto compile the Keycloak configuration in advance.
2. Modify the ExecStart section in the /etc/systemd/system/X4-Authentication-Provider.service file as follows: Replace start-dev with start.