Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bitnami/keycloak]: add url env vars to fix admin ingress access #25386

Merged
merged 2 commits into from
Apr 29, 2024

Conversation

MrFreezeex
Copy link
Contributor

@MrFreezeex MrFreezeex commented Apr 25, 2024

Description of the change

Replace KC_HOSTNAME_ADMIN by KC_HOSTNAME_ADMIN_URL to include the scheme (http or https) and add KC_HOSTNAME_URL for the frontend to function correctly. These variable allow the front to function correctly if we have the tls option enabled. Before this commit the front was always attempting to load some resources over http while it may be exposed in https.

Benefits

Keycloak admin ingress works if tls/https is configured

Possible drawbacks

If some users defined KC_HOSTNAME or KC_HOSTNAME_URL in extraEnv it could prevent keycloak to start, I reduced the risk by adding this variable only if the ingress is not enabled though

Applicable issues

Additional information

Checklist

  • Chart version bumped in Chart.yaml according to semver. This is not necessary when the changes only affect README.md files.
  • Variables are documented in the values.yaml and added to the README.md using readme-generator-for-helm
  • Title of the pull request follows this pattern [bitnami/<name_of_the_chart>] Descriptive title
  • All commits signed off and in agreement of Developer Certificate of Origin (DCO)

@github-actions github-actions bot added keycloak triage Triage is needed labels Apr 25, 2024
@github-actions github-actions bot requested a review from carrodher April 25, 2024 12:01
@MrFreezeex MrFreezeex force-pushed the keycloak-fix-admin-ingress-env branch 2 times, most recently from ddc7de3 to 92a38c8 Compare April 25, 2024 13:39
@carrodher
Copy link
Member

Thanks for your contribution, due to some changes in our test suite it is needed to rebase from main and the update the PR, could you please do that? Thanks beforehand and sorry for the inconvenience.

@MrFreezeex MrFreezeex force-pushed the keycloak-fix-admin-ingress-env branch from 92a38c8 to 763b079 Compare April 26, 2024 07:56
@MrFreezeex
Copy link
Contributor Author

Thanks for your contribution, due to some changes in our test suite it is needed to rebase from main and the update the PR, could you please do that? Thanks beforehand and sorry for the inconvenience.

Sure, no worries!

@carrodher carrodher added verify Execute verification workflow for these changes in-progress labels Apr 27, 2024
@github-actions github-actions bot removed the triage Triage is needed label Apr 27, 2024
@github-actions github-actions bot removed the request for review from carrodher April 27, 2024 07:43
@jotamartos
Copy link
Contributor

Hi @MrFreezeex,

Thanks for creating this PR. Could you please take a look at my suggestions? I think the URL is not generated properly.

Replace KC_HOSTNAME_ADMIN by KC_HOSTNAME_ADMIN_URL to include the scheme
(http or https) and add KC_HOSTNAME_URL for the frontend to function
correctly. These variable allow the front to function correctly if we
have the tls option enabled. Before this commit the front was always
attempting to load some resources over http while it may be exposed in
https.

Signed-off-by: Arthur Outhenin-Chalandre <arthur.outhenin-chalandre@ledger.fr>
Signed-off-by: Arthur Outhenin-Chalandre <arthur.outhenin-chalandre@ledger.fr>
@MrFreezeex MrFreezeex force-pushed the keycloak-fix-admin-ingress-env branch from e246ba1 to 36eaa7f Compare April 29, 2024 10:20
@MrFreezeex
Copy link
Contributor Author

MrFreezeex commented Apr 29, 2024

Hi @MrFreezeex,

Thanks for creating this PR. Could you please take a look at my suggestions? I think the URL is not generated properly.

Woops indeed sorry for that and thanks for catching it! I just fixed it

Copy link
Contributor

@jotamartos jotamartos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Thanks for your contribution.

@jotamartos jotamartos merged commit 43ccdb2 into bitnami:main Apr 29, 2024
8 checks passed
@MrFreezeex MrFreezeex deleted the keycloak-fix-admin-ingress-env branch April 29, 2024 13:40
matheusmgon pushed a commit to matheusmgon/charts that referenced this pull request May 2, 2024
…nami#25386)

* [bitnami/keycloak]: add url env vars to fix admin ingress access

Replace KC_HOSTNAME_ADMIN by KC_HOSTNAME_ADMIN_URL to include the scheme
(http or https) and add KC_HOSTNAME_URL for the frontend to function
correctly. These variable allow the front to function correctly if we
have the tls option enabled. Before this commit the front was always
attempting to load some resources over http while it may be exposed in
https.

Signed-off-by: Arthur Outhenin-Chalandre <arthur.outhenin-chalandre@ledger.fr>

* [bitnami/keycloak]: fix license header to fix the CI

Signed-off-by: Arthur Outhenin-Chalandre <arthur.outhenin-chalandre@ledger.fr>

---------

Signed-off-by: Arthur Outhenin-Chalandre <arthur.outhenin-chalandre@ledger.fr>
Signed-off-by: Matheus Goncalves <matheus.goncalves@bexio.com>
matheusmgon pushed a commit to matheusmgon/charts that referenced this pull request May 3, 2024
…nami#25386)

* [bitnami/keycloak]: add url env vars to fix admin ingress access

Replace KC_HOSTNAME_ADMIN by KC_HOSTNAME_ADMIN_URL to include the scheme
(http or https) and add KC_HOSTNAME_URL for the frontend to function
correctly. These variable allow the front to function correctly if we
have the tls option enabled. Before this commit the front was always
attempting to load some resources over http while it may be exposed in
https.

Signed-off-by: Arthur Outhenin-Chalandre <arthur.outhenin-chalandre@ledger.fr>

* [bitnami/keycloak]: fix license header to fix the CI

Signed-off-by: Arthur Outhenin-Chalandre <arthur.outhenin-chalandre@ledger.fr>

---------

Signed-off-by: Arthur Outhenin-Chalandre <arthur.outhenin-chalandre@ledger.fr>
Signed-off-by: Matheus Goncalves <matheus.goncalves@bexio.com>
matheusmgon pushed a commit to matheusmgon/charts that referenced this pull request May 7, 2024
…nami#25386)

* [bitnami/keycloak]: add url env vars to fix admin ingress access

Replace KC_HOSTNAME_ADMIN by KC_HOSTNAME_ADMIN_URL to include the scheme
(http or https) and add KC_HOSTNAME_URL for the frontend to function
correctly. These variable allow the front to function correctly if we
have the tls option enabled. Before this commit the front was always
attempting to load some resources over http while it may be exposed in
https.

Signed-off-by: Arthur Outhenin-Chalandre <arthur.outhenin-chalandre@ledger.fr>

* [bitnami/keycloak]: fix license header to fix the CI

Signed-off-by: Arthur Outhenin-Chalandre <arthur.outhenin-chalandre@ledger.fr>

---------

Signed-off-by: Arthur Outhenin-Chalandre <arthur.outhenin-chalandre@ledger.fr>
Signed-off-by: Matheus Gonçalves <mathmgoncalves@gmail.com>
matheusmgon pushed a commit to matheusmgon/charts that referenced this pull request May 8, 2024
…nami#25386)

* [bitnami/keycloak]: add url env vars to fix admin ingress access

Replace KC_HOSTNAME_ADMIN by KC_HOSTNAME_ADMIN_URL to include the scheme
(http or https) and add KC_HOSTNAME_URL for the frontend to function
correctly. These variable allow the front to function correctly if we
have the tls option enabled. Before this commit the front was always
attempting to load some resources over http while it may be exposed in
https.

Signed-off-by: Arthur Outhenin-Chalandre <arthur.outhenin-chalandre@ledger.fr>

* [bitnami/keycloak]: fix license header to fix the CI

Signed-off-by: Arthur Outhenin-Chalandre <arthur.outhenin-chalandre@ledger.fr>

---------

Signed-off-by: Arthur Outhenin-Chalandre <arthur.outhenin-chalandre@ledger.fr>
Signed-off-by: Matheus Gonçalves <mathmgoncalves@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
keycloak solved verify Execute verification workflow for these changes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants