Details
Description
There are a number of configuration attributes on the "Connector" element in server.xml. For a stand alone local configuration, the ability to control the settings for the JSSE based implementation of SSL/TLS support would make testing against a secured Tomcat with Cargo far easier.
The attached patch adds support for the configuration of the server key store, trust store, client authentication, and protocol settings.
The patch adds 2 checkstyle violations relating to complexity; however, the metrics do not reflect the real-world simplicity of the method implementation and can be considered false positives.
I did not see any integration tests that examine the resulting server.xml file and therefore did not include tests of the new features. I tested the updated code against the project I am working on. If there are automated tests of this aspect of the container support, please indicate where these reside and I will happily add the new features to the test.
Finally, the documentation that enumerates the container configuration options is generated by the build. Is there anything specific that I need to do in the code base to ensure that the new options appear in the documentation?
Issue Links
- is duplicated by
-
CARGO-1134
Cannot enable SSL on Tomcat 5.x, 6.x, and 7.x standalone local configuration
-
- is related to
-
CARGO-574
Support simultaneous http and https connectors in tomcat5x
-
-
CARGO-977
HTTPS (cargo.protocol) support for Jetty 6.x, 7.x
-
-
CARGO-1030
support both http and https configuration
-
Hi David
The patch looks very good. In order to add tests, what you need to do is to add the to the core/samples/java Maven artifact. That one has, in tests, the org.codehaus.cargo.sample.java.tomcat package which contains Tomcat-specific tests.
This way, we do not test what is in the server.xml but that what is attempted to be set actually works as expected
Let me know when ready -I'll then give you developer access.
Thank you