On Jul 16, 2012, at 6:42 PM, Smithies, Russell wrote:
I have a situation I’m sure others have faced but I can’t see how to solve it
without hacking the src and I’d rather not do that just yet as it complicates
upgrades.
We’re using Apache with NTLM and “require valid user” so it’s a
IANAAG, but the following should be secure and effective as well (at least
it works for me), setting REMOTE_USER with an Apache authentication module
in conjunction with ProxyPass
RequestHeader set REMOTE_USER %{REMOTE_USER}s
RequestHeader edit REMOTE_USER ^.*(.+?) $1
Cheers,
Paul
On
I have a situation I'm sure others have faced but I can't see how to solve it
without hacking the src and I'd rather not do that just yet as it complicates
upgrades.
We're using Apache with NTLM and require valid user so it's a corporate
domain and only authorized users are allowed access.
If