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

use X-forward-for address instead of the load balancer ip. #4209

Closed
gaaray2k opened this issue Jul 13, 2020 · 4 comments
Closed

use X-forward-for address instead of the load balancer ip. #4209

gaaray2k opened this issue Jul 13, 2020 · 4 comments

Comments

@gaaray2k
Copy link

When I log into primate an event is recorded saying "user USER logged in from IPADDRESS". this is a problem for users that use a proxy or load balancer because the ip will always be the the ip of the load balancer or proxy. can a system config option be added to use the IP address of the x-forward header so the real ip of the user is shown instead when using a proxy or load balancer?.

@ravening
Copy link
Member

we are using haproxy as a loadbalancer and when transparent mode is enabled, it uses XFF address instead of loadbalancer ip. This will be fixed in #4141

@gaaray2k
Copy link
Author

gaaray2k commented Jul 30, 2020

Sorry I don't think I was clear enough. In primate, when a user logs in, an event is logged that has the IP of the user in it. The problem is that placing a load balancer in front of the management server, the IP is the load balancer is in the event instead of the client IP. I asked in the primate project about this and they said that they just take whatever IP the backend sends primate. So my question is, is there a way to make the backend log the IP in the x- forward header?

@DaanHoogland
Copy link
Contributor

@gaaray2k did you get any progres on this or is it still an issue/feature request?

@DaanHoogland
Copy link
Contributor

@gaaray2k closing, hope you don't mind.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants