[bitnami/keycloak] Wildfly based configuration for Keycloak Quarkus edition

[ice09]

Name and Version

bitname/keycloak

What architecture are you using?

None

What steps will reproduce the bug?

1. see https://github.com/bitnami/containers/tree/main/bitnami/keycloak#configuration
2. there are several Wildfly-based configuration parameters like KEYCLOAK_MANAGEMENT_USER

What is the expected behavior?

As Keycloak is Quarkus based since several versions, Wildfly is not used anymore and the configuration should not work.

What do you see instead?

Wildfly-based configuration parameters.

Additional information

No response

[carrodher]

Thanks for creating this issue and the associated PR. The team will review it and provide feedback. Once merged the PR, this issue will be automatically closed.

[ice09]

Please check the "Full Configuration" section, as far as I understand the mentioned standalone.xml configuration is not valid any more.

[carrodher]

Thanks for reporting this issue. Would you like to contribute by creating a PR to solve the issue? The Bitnami team will be happy to review it and provide feedback. Here you can find the contributing guidelines.

[ice09]

Actually, I can't - I don't know what you want to do about this section. Personally, I would delete it as I think there is no such possibility of a full configuration with the Quarkus edition, but I am not sure.

[juan131]

Hi @ice09

As you can check in the piece of code's below, the init logic is actually copying any configuration file included at the mounted directory indicated at KEYCLOAK_MOUNTED_CONF_DIR to the Keycloak's configuration directory.

• https://github.com/bitnami/containers/blob/main/bitnami/keycloak/21/debian-11/rootfs/opt/bitnami/scripts/libkeycloak.sh#L314-L316

However, the README's is incorrect since it's mentioning the old Wildfly-based configuration file as an example. I created a PR to address this issue.