Closed eladkug closed 3 years ago
@jvanderhoof Are you going to fix this issue?
@jvanderhoof ?
Is this perhaps related to the concept of trusted proxies? Wondering if @cyberark/conjur-core-team has any feedback they can share about the recommended way to use Conjur OSS to accurately reflect the client IP in the logs.
@eladkug, I don't think there is a release of Conjur with the trusted proxy functionality in place, but if you build one, the TRUSTED_PROXIES
environment variable should allow you to remove Nginx: https://github.com/cyberark/conjur/blob/master/CHANGELOG.md#added
@jvanderhoof now that we've tagged v1.10.0, is that a valid version to use with the trusted proxies functionality?
this seems like a reasonable blog post - anyone have interest in writing it? :) could demonstrate using trusted proxies with the quick start vs helm chart
@jvanderhoof but i will still see Nginx IP as origin instead of our IP machine?
The fix and tests were added here: https://github.com/cyberark/conjur/pull/1726/files. The GH issue was not the driving force for this PR. The work with Epic was the driver. As a result, this bug was not closed. Closing now.
Summary
While we are working with Oss and Ngnix direct access will not works. We are identified the Nginx container IP instead of the Client IP
Steps to Reproduce
Steps to reproduce the behavior:
"IPAddress": "192.168.32.2"