I have set up an Azure Container Instance with software that uses Single-Sign-On to access its services. It uses client public IP to prevent session hijack attacks and also to handle session tickets.
This feature is not working because the container instance receives all incoming client IPs masqueraded behind private IPs (10.x.x.x.). It also gets worst due to an internal load balancing (not set up from my side) that makes client IPs change from request to request, invalidating session tickets.
We tried to retrieve public client IP using the X-Forwarded-For header to overcome the probable proxy or internal load balancer; it didn't work.
So, there is a setup parameter or network configuration that makes the container instance retrieve client public IPs?