I understand full implementation of this will be tricky. Particularly when it comes to trusting the proxy enough for ScreenConnect to act on the relayed headers.

But please, PLEASE, at least add the x-forwarded-for header IP to the logs. Tag it as an information only, proxy-reported IP. A simple text entry with no action. That much should be a very simple addition.

Yeah, the failed login logs aren't particularly helpful when all you see is your own proxy IP. 

I'll second (or third?) the request that this be given immediate attention. You don't even have to go all-in on the integration and proxy trust. I'd be happy if you just logged the x-real-ip or x-forwarded-for header and included it in the audit report. Call it a "proxy reported IP" line or something. 

It no longer works for me, even in the same version it previously worked in. I haven't taken the time to troubleshoot the cause, but I think it may be a recent windows update. 

Tested and confirmed working. Thanks Carl Green!

This really seems like more of a bug than a feature request. But whatever the case, I'm asking for it to be fixed/feature added too.