Hi,

In your SSO authentication activity you can access a HTTPServletRequest facade object and access HTTP Request headers and general request object methods. This can be used to get the client IP address. However, it depends on other infrastructure in place between the client browser and PRPC.

It's very unlikely that you will have clients connecting right to the PRPC JVM. You will probably have many JVM nodes and web servers and load balancers in front of PRPC. For example:

Browser->Cisco F5->Web Server(More than 1)->PRPC Node(More than 1)

What you don't want to get is the IP address of the middleware components between the client browser and PRPC.

For example:

request.getRemoteAddr()

This will return the IP address of the incoming connection that could be the web server or load balancer IP address.  In the example above the getRemoteAddr method would return the IP address of the web server.

As the middleware components route the traffic to the JVM they can and usually will add a HTTP header containing the client ip address.

Update your login activity and the following code to a new Java step right at the top of the activity:

javax.servlet.http.HttpServletRequest request =    (javax.servlet.http.HttpServletRequest)tools.getRequestor().getRequestorPage().getObject("pxHTTPServletRequest");
/* Debug only, comment out when done testing */
oLog.infoForced("Incoming headers for login:");
java.util.Enumeration e = request.getHeaderNames();
String header = null;
while (e.hasMoreElements()) {
      header = (String) e.nextElement();
      oLog.infoForced(header + ": " + request.getHeader(header));      
}

This will output to the logfile all the HTTP headers of the incoming request.

Make sure the login activity is checked in and test the login. 

Get the logfiles and look to see if you have the  client IP address contained in one of the headers?

Yes:

Easy, you just need to get the header value. Not sure what you need to do with it so just putting it in a local variable defined in the activity.

1. Define a local string variable on the Parameters tab of the activity: clientIP

2. Comment out the logging for the output of all header.

3. Set clientIP from the http header:

javax.servlet.http.HttpServletRequest request =    (javax.servlet.http.HttpServletRequest)tools.getRequestor().getRequestorPage().getObject("pxHTTPServletRequest");
/* Debug only, comment out when done testing 
oLog.infoForced("Incoming headers for login:");
java.util.Enumeration e = request.getHeaderNames();
String header = null;
while (e.hasMoreElements()) {
      header = (String) e.nextElement();
      oLog.infoForced(header + ": " + request.getHeader(header));      
}
*/

clientIP = request.getHeader(“<headerName>”);

Now you can you use this variable for other processing in the activity. (Local.clientIP)

No:

If you don’t see a header with the client value then it's time to send an email to the owners of the middleware components and ask them to add the client IP address to a HTTP header. It’s important that you contact the right team. In the example above you would need to contact the Cisco F5 admin to get the client IP added. Why? Because it’s the first middleware component the browser talks to.

Hope this helps.

Hi,

In your SSO authentication activity you can access a HTTPServletRequest facade object and access HTTP Request headers and general request object methods. This can be used to get the client IP address. However, it depends on other infrastructure in place between the client browser and PRPC.

It's very unlikely that you will have clients connecting right to the PRPC JVM. You will probably have many JVM nodes and web servers and load balancers in front of PRPC. For example:

Browser->Cisco F5->Web Server(More than 1)->PRPC Node(More than 1)

What you don't want to get is the IP address of the middleware components between the client browser and PRPC.

For example:

request.getRemoteAddr()

This will return the IP address of the incoming connection that could be the web server or load balancer IP address.  In the example above the getRemoteAddr method would return the IP address of the web server.

As the middleware components route the traffic to the JVM they can and usually will add a HTTP header containing the client ip address.

Update your login activity and the following code to a new Java step right at the top of the activity:

javax.servlet.http.HttpServletRequest request =    (javax.servlet.http.HttpServletRequest)tools.getRequestor().getRequestorPage().getObject("pxHTTPServletRequest");
/* Debug only, comment out when done testing */
oLog.infoForced("Incoming headers for login:");
java.util.Enumeration e = request.getHeaderNames();
String header = null;
while (e.hasMoreElements()) {
      header = (String) e.nextElement();
      oLog.infoForced(header + ": " + request.getHeader(header));      
}

This will output to the logfile all the HTTP headers of the incoming request.

Make sure the login activity is checked in and test the login. 

Get the logfiles and look to see if you have the  client IP address contained in one of the headers?

Yes:

Easy, you just need to get the header value. Not sure what you need to do with it so just putting it in a local variable defined in the activity.

1. Define a local string variable on the Parameters tab of the activity: clientIP

2. Comment out the logging for the output of all header.

3. Set clientIP from the http header:

javax.servlet.http.HttpServletRequest request =    (javax.servlet.http.HttpServletRequest)tools.getRequestor().getRequestorPage().getObject("pxHTTPServletRequest");
/* Debug only, comment out when done testing 
oLog.infoForced("Incoming headers for login:");
java.util.Enumeration e = request.getHeaderNames();
String header = null;
while (e.hasMoreElements()) {
      header = (String) e.nextElement();
      oLog.infoForced(header + ": " + request.getHeader(header));      
}
*/

clientIP = request.getHeader(“<headerName>”);

Now you can you use this variable for other processing in the activity. (Local.clientIP)

No:

If you don’t see a header with the client value then it's time to send an email to the owners of the middleware components and ask them to add the client IP address to a HTTP header. It’s important that you contact the right team. In the example above you would need to contact the Cisco F5 admin to get the client IP added. Why? Because it’s the first middleware component the browser talks to.

Hope this helps.