Issue IP-Based Allow/Block Validation Login Peoplesoft in Production Environment -PeopleTools 8.61

We are using a custom sign-on PeopleCode to validate user logins based on IP address allow/block Login. As part of this logic, we are retrieving the client IP address using %Request.GetHeader("X-Forwarded-For").
This implementation works as expected in all non-production environments, where the correct client IP address is returned.

However, in the production environment, the same logic returns a different IP address. Due to this discrepancy, users who should be blocked based on their IP are instead being allowed access.

Could you please let us know if there is any specific setup or configuration required in PeopleSoft or server level to correctly pass or preserve the X-Forwarded-For header? We would like to understand if any production-specific configuration might be affecting how the client IP address is being forwarded or interpreted.