We are trying to record the requestors ip address when providing invalid login credentials in custom authentication process however the values are not present in the expected location of pxReqRemoteAddr or pxReqRemoteHost on the pxRequestor page.
***Updated by moderator: Lochan to add SR details***
We are in 7.2 and the instance is hosted on Pega cloud. Currently I am testing this with direct access to the single node dev environment but once in prod we will be using a load balancer. pxReqServer=Apache Tomcat/7.0.73 and pxReqServerPort=443. So as it seems this is working as expected, do we have another way to collect that information for audit purposes?
Posted: 5 years ago
Posted: 17 May 2017 15:06 EDT
David Kircheis (David+Kircheis)
Product Manager - Cloud
If you are going to be using a Load Balancer (which is ,amongst other things: a Reverse Proxy); then (at least in all cases of Load Balancer implementations I have seen) the App Server won't be aware of the external IP address of the incoming request; it will see all traffic originating from the Load Balancer.
Do you know if your Load Balancer is able to 'inject' arbitary cookies/HTTP-Headers ? (if it is Apache 'modproxy' for instance : then it can) - you could consider recording the original IP address this in a HTTP header in this way. (say as a cookie 'original-ip-address:xx.xx.xx.xx').
Then on the PRPC side - you *should* (perhaps with a little customisation - I'm not actually 100% sure actually how you would do this) be able to check for the HTTP cookies/Headers and record your audit trail that way ?
Posted: 5 years ago
Posted: 30 May 2017 15:46 EDT
Marissa Rogers (MarissaRogers)
Senior Knowledge Management Specialist
Upon reviewing the associated SR, it has been closed as this is no longer a requirement for you. I'll be closing this to future comments. If you still need assistance or another user has the same question, please open a new post.