
ZoeQ.25664 (Customer) asked a question.
I have a use case that there are api requests from different clients with different public IPs, these info get saved in the request header "X-Forwarded-For". However, the centralised api server sits behind a proxy with a unique IP(ip2). In this case, I can see in the Okta system log that client.ip is ip2, and end users' public ip shows in the IP chains.
This causes false alarm because Okta counts all the api requests based on ip2. I am wondering if it is possible to configure Okta so the api requests are grouped by the real end user's ip, not the proxy ip.

Hello @ZoeQ.25664 (Customer) Thank you for reacting out to our Community!
At this time, this is expected behaviour on our side, please see our documentation for a better understanding of how we evaluate the IP's:
https://support.okta.com/help/s/article/How-is-Okta-evaluating-my-IP-address?language=en_US
However you can add a Feature Request on our Idea section, for a chance that this functionality to be added in the future.
https://support.okta.com/help/s/ideas
The Okta Community Catalysts Program is now live. Collect online badges when you participate in the Okta Help Center Questions community. Learn more here.