You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The last login ip will show the ip of the LoadBalancer not the IP of the User... 😳
Warning Spoilers:
The challenge to override the Last Login IP will most likely also not work in most cloud setups as the initial Cloud Loadbalancer will most likely strip away the X-Forwarded-For headers set by the user.
The text was updated successfully, but these errors were encountered:
Mh yeah that might be an option.
But it should probably work correctly on "normal" docker setups right, meaning setups without a loadbalancer in front of it.
Just checked the code of the challenge, and it doesn't use XFF for that matter but the True-Client-IP header. So it should work just fine even behind a load balancer.
The last login ip will show the ip of the LoadBalancer not the IP of the User... 😳
Warning Spoilers:
The challenge to override the Last Login IP will most likely also not work in most cloud setups as the initial Cloud Loadbalancer will most likely strip away the
X-Forwarded-For
headers set by the user.The text was updated successfully, but these errors were encountered: