
eobz3 (eobz3) asked a question.
Hi,
I noticed that when connected to corporate VPN authenticated with Okta, the user's source IP address is the home local IP address and not the corporate IP address. Is this part of the configuration? I'm looking at the source IP address would reflect the corporate's IP address.
Thanks.

Hello @eobz3 (eobz3) Thank you for reaching out to our Community!
This is expected behaviour, the user's IP address will still be present in the IP chain however the Proxy IP address will also show there. please see our articles on this matter:
https://support.okta.com/help/s/article/How-is-Okta-evaluating-my-IP-address?language=en_US
https://support.okta.com/help/s/article/What-is-the-second-other-IP-in-the-IP-chain-in-System-Logs-referring-to?language=en_US
Hope this helps!
Thanks. Further question to this. I have AWS services which I want to restrict based on geo locations and IP addresses range. When user connects to the AWS services, the IP address presented in the request is the home local IP address when connected to corporate VPN authenticated via Okta. Is the IP address in the request presented by Okta? So in this use case, the legitimate user will be blocked as the IP address will be out of Corporate IP address range.