[ 
https://issues.apache.org/jira/browse/MTOMCAT-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13559228#comment-13559228
 ] 

Marcel Silberhorn commented on MTOMCAT-190:
-------------------------------------------

Dear [~gmazza]

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:
{noformat} -clientAuth                            enable client authentication 
for
                                        https
{noformat}

will this fix my "problem"?
                
> Client Certificate settings for connector
> -----------------------------------------
>
>                 Key: MTOMCAT-190
>                 URL: https://issues.apache.org/jira/browse/MTOMCAT-190
>             Project: Apache Tomcat Maven Plugin
>          Issue Type: Improvement
>          Components: tomcat7
>    Affects Versions: 2.0
>            Reporter: Marcel Silberhorn
>            Assignee: Olivier Lamy (*$^¨%`£)
>              Labels: connector
>             Fix For: 2.1
>
>
> currently there seems to be no way to configure SSL connector settings like 
> clientAuth what make it useless for certain certificate login tests and I 
> always need a second, manually installed instance of Tomcat for this but I'm 
> not able to just run {{tomcat7:run}}
> So it would be great so see some clientCert options in an upcoming version!

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Reply via email to