You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by "Olivier Lamy (*$^¨%`£ JIRA)" <ji...@apache.org> on 2013/11/01 11:33:19 UTC
[jira] [Updated] (MTOMCAT-222) No (documented) way to tolerate
server cert whose CN doesn't match DNS hostname
[ https://issues.apache.org/jira/browse/MTOMCAT-222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Olivier Lamy (*$^¨%`£) updated MTOMCAT-222:
-------------------------------------------
Fix Version/s: backlog
> No (documented) way to tolerate server cert whose CN doesn't match DNS hostname
> -------------------------------------------------------------------------------
>
> Key: MTOMCAT-222
> URL: https://issues.apache.org/jira/browse/MTOMCAT-222
> Project: Apache Tomcat Maven Plugin
> Issue Type: Improvement
> Components: tomcat7
> Affects Versions: 2.0-beta-1, 2.1
> Environment: Ubuntu 12.0.4, Maven 3.0.4 and 3.0.5
> Reporter: Chris Owens
> Assignee: Olivier Lamy (*$^¨%`£)
> Fix For: backlog
>
>
> When invoking goal tomcat7:deploy to a ssl server, if the common name in the server's certificate doesn't match the hostname, the deployment fails. That is probably correct for a production environment, but often, in test, there are lots of servers with fairly random ssl certs. It would be very helpful to have a way, within the plugin configuration, to instruct the plugin to tolerate a mismatch.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org