How to resolve the issue of logging proxy server IP address for every request
2 years ago
Originally Published: 2008-02-28
Article Number
000061746
Issue
How to resolve the issue of logging proxy server IP address for every request
customer observed form Forensic Summary reports or audit log that proxy server's IP address are logged for every request
Resolution

For standalone model of the system, you need to configure the file, config-clientenv.xml, in WEB-INF/CLASSES folder. The file defines the pointer and parameter for your application server. The settings are:

Default URL - the default URL for your application server and is used to post the password page. This page can also redirect the user to other bank actions, like maintenance, cancel actions, etc. This URL is used as a backup for the return URL location sent with the cookie.

 <entry key="default">

<value>http://d3.passmarksecurity.com/largebank_client/

resultDispatcherAction.do</value>

</entry>

Note: This URL can be defined as part of the command token (request message) between the System and your application server; however, if the URL is missing in the API, then this default URL is used instead.

URL for Errors - the URL to go to upon error detection.

<entry key="error">

<value>http://d3.passmarksecurity.com/largebank_client/

Error.jsp</value>

</entry>

 

Reverse Proxies - if you are using a reverse proxy in the middle, the RSA server collects the IP addresses from the x-forwarded-for, rather than from ??RequestedRemoteAddr

<!-- list of trusted proxy IPs -->

<bean id="com.passmarksecurity.utils.HttpUtils" class="com.passmarksecurity.utils.HttpUtils">

<property name="trustedProxiList">

<list>

<value>127.0.0.1</value>

<value>xx.xx.xx.xx</value>

</list>

</property>

</bean>


For webservices model, add following entries in c-application-context.xml

<bean class="com.passmarksecurity.utils.RemoteAddrUtils" id="com.passmarksecurity.utils.RemoteAddrUtils">
  <property name="trustedProxyList">
   <list/>
  </property>
 </bean>