<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D54z00008CPzjwCADOkta Classic EngineAPI Access ManagementAnswered2022-10-13T17:03:17.000Z2022-10-12T04:38:32.000Z2022-10-13T17:03:17.000Z

ZoeQ.25664 (Customer) asked a question.

Does Okta monitor the api rate limit via client.ip?

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.


This question is closed.
Loading
Does Okta monitor the api rate limit via client.ip?