Has anyone successfully implemented new feature Remote Client Directives ?
We are using Azure Application Gateway (AGW) as the load balancer for our PeopleSoft environment. By default, the PSACCESSLOG table captures the IP address of the immediate upstream device communicating with the PeopleSoft Internet Architecture (PIA) web server. As a result, when PeopleSoft is hosted behind Azure Application Gateway, the LOGIPADDRESS field records the internal Application Gateway IP address rather than the actual client IP address of the end user.
To address this, we configured the Remote Client Directives settings in the PeopleSoft Web Profile and added the appropriate header information on the Remote Client Directives tab. However, after applying the changes and validating the configuration, the behavior remains unchanged, and the LOGIPADDRESS field continues to display the Application Gateway IP instead of the originating client IP address.