tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Olivier Lamy (*$^¨%`£) (JIRA) <j...@apache.org>
Subject [jira] [Updated] (MTOMCAT-222) No (documented) way to tolerate server cert whose CN doesn't match DNS hostname
Date Fri, 01 Nov 2013 10:33:19 GMT

     [ 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


Mime
View raw message