Open GoogleCodeExporter opened 9 years ago
Oops, left a trace in there.
Original comment by EsmondP...@gmail.com
on 13 Dec 2011 at 4:25
Attachments:
I finally solved this a completely different way, by putting an Apache HTTPD in
front of Tomcat. This allows for much more fine-grained control over SSL down
to the <Directory> or <Location> level, such that you can change cipher suites,
use different certificates and CA certs, want/need client authentication, right
down to the bottom level, rather than be stuck with it all on or off as you are
with Tomcat. This is a far better solution so the attached patches can probably
be disregarded in favour of documenting this solution. Now that I've put Apache
HTTPD in front I am wondering why I didn't do it years ago.
Original comment by EsmondP...@gmail.com
on 30 May 2012 at 8:16
Note that the AuthenticationRequestImpl.java attached to this question neither
compiles nor runs under Tomcat 7. The Apache HTTPD solution above is a much
better technique all round.
Original comment by EsmondP...@gmail.com
on 12 Jul 2012 at 9:57
Original issue reported on code.google.com by
EsmondP...@gmail.com
on 13 Dec 2011 at 4:04Attachments: