Mike Murray wrote: > I'm investigating using Apache and SSL for (reverse) proxying HTTPS requests; > however, one of the requirements of the task is to have a strong auth > mechanism in place. > > I had two ideas, both of which have lead me to a dead end: > > 1. Use the ProxyPass and ProxyPassReverse directives to authorize > connections, and requiring client certs to authenticate to the server.
This should work fine.
> 2. Using a normal SSL page to authenticate via client certs, and using an
> .htaccess file in the DocRoot of the proxy server to auth IP addresses.
This won't work - as there is no concept of a root directory for a
proxied server. Put your directives within a <Location> tag in the main
server.
> Both seemed likely, and both have failed. The first because the directives
> don't work as I had hoped
How didn't it work?
Regards,
Graham
--
-----------------------------------------
[EMAIL PROTECTED] "There's a moon
over Bourbon Street
tonight..."
smime.p7s
Description: S/MIME Cryptographic Signature
