Dear Glen Mazza
It's not production where this option is needed.
For sure, mvn-tomcat is for development and integration-tests only!
But please think about those who are writing security / authentication / authorization related things like filter. While jetty doesn't like filter chains (it's not possible to determine the right chain ordering for jetty) nor tomcat7:run will ask for x509 based authentication I have to manually deploy the webapp to a single tomcat instance which I have to setup (each developer has to know how too) or (more practically) have to use Eclipse WTP Tomcat Plugin instead of mvn-tomcat but have to download and "install" eclipse and did have this WTP thing many developers are getting into trouble with ;/ .
So nevertheless it's used seldom: where is the problem, for me it's just one parameter in the servers connector settings.
I currently doesn't understand the barriers.
The certificates for the container are typically used from the users local keychain ~/.keystore
Please let me know if I can do anything ...
P.S: found this site: http://tomcat.apache.org/maven-plugin-2.0/executable-war-jar.html with the option list at the end:
-clientAuth enable client authentication for
will this fix my "problem"?