Support Article

Unable to update properties on pxRequestor Page

SA-38559

Summary



User is using reverse proxy(Elastic LB) to access Pega and Pega is showing Elastic Load Balancer's IP instead of User's IP.
User is getting the remote IP through single sign-on and trying to update as following, so that logs would reflect the correct IP.

When trying to update the following properties on pxRequestor page, the updated values does not appear on the clipboard.
  • pxReqRemoteAddr
  • pxReqRemoteHost


Error Messages



Not applicable

Steps to Reproduce



Use an activity with Property-Set or Java to update pxReqRemoteAddr & pxReqRemoteHost properties on pxRequestor page.


Root Cause



Updating the pxRequestor(read-only) page by using any rules is not possible as it only gets populated at the engine initialization(code) level.

Resolution



Make the following change to the operating environment:

User has Tomcat server and can leverage RemoteIpValve property to get the x-forwaded-for value as remote IP address.

To have this configuration, update the server.xml and restart the Pega servers.

<Valve className="org.apache.catalina.valves.RemoteIpValve"
remotelpHeader="x-forwarded-for"
proxiesHeader="x-forwarded-by"

protocolHeader="x-forwarded-proto" />


This will ensure to capture the remote client global IP address instead of ELB’s IP in pxReqRemoteAddr property.

Published May 26, 2017 - Updated July 3, 2017

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.