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] keycloak behind traefik works but doesn't log the client ip #30627

Open
mhazan01 opened this issue Nov 26, 2024 · 1 comment
Assignees
Labels
keycloak tech-issues The user has a technical issue about an application triage Triage is needed

Comments

@mhazan01
Copy link

mhazan01 commented Nov 26, 2024

Name and Version

bitnami/keycloak latest

What architecture are you using?

amd64

What steps will reproduce the bug?

helm install keycloak oci://registry-1.docker.io/bitnamicharts/keycloak --create-namespace -n keycloak -f values.yaml
values.yaml contain configuration for ingress with traefik

Are you using any custom parameters or values?

ingress:
  ingressClassName: "traefik"
extraEnvVars:
  - name: PROXY_ADDRESS_FORWARDING
    value: "true" 

What is the expected behavior?

keycloak logs show real client ip

What do you see instead?

keycloak logs show loadbalancer ip

Additional information

i've been able to get the real client ip on the whoami container, using forwardedHeaders: and proxyProtocol: but i'am unable to reproduce the configuration in the keycloak chart, i assumed PROXY_ADDRESS_FORWARDING was it. anyone able to help me figure out where and which parameters to add in the chart ?

@mhazan01 mhazan01 added the tech-issues The user has a technical issue about an application label Nov 26, 2024
@github-actions github-actions bot added the triage Triage is needed label Nov 26, 2024
@javsalgar javsalgar changed the title keycloak behind traefik works but doesn't log the client ip [bitnami/keycloak] keycloak behind traefik works but doesn't log the client ip Nov 27, 2024
@javsalgar
Copy link
Contributor

Hi, the issue may not be directly related to the Bitnami container image/Helm chart, but rather to how the application is being utilized, configured in your specific environment, or tied to a particular scenario that is not easy to reproduce on our side.

If you think that's not the case and want to contribute a solution, we'd like to invite you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.

Your contribution will greatly benefit the community. Please feel free to contact us if you have any questions or need assistance.

Suppose you have any questions about the application, customizing its content, or technology and infrastructure usage. In that case, we highly recommend that you refer to the forums and user guides provided by the project responsible for the application or technology.

With that said, we'll keep this ticket open until the stale bot automatically closes it, in case someone from the community contributes valuable insights.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
keycloak tech-issues The user has a technical issue about an application triage Triage is needed
Projects
None yet
Development

No branches or pull requests

2 participants