[
https://issues.apache.org/jira/browse/MTOMCAT-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brad Giaccio updated MTOMCAT-108:
---------------------------------
Attachment: https.patch
I've tested this patch on Mac OSX 10.6.8, Fedora Core 16, and Redhat Linux 5.4
It handles, httpPort not being set so only https starts up
it adds 3 options to the startup
-keyAlias
-clientAuth
It checks for the 6 -Djavax.net.ssl properties for setting up key and trust
stores
I also added PasswordUtil to allow the passwords to be obfuscated (a security
requirement for some systems is no passwords in clear text ... I know
obfuscation is like closing your front door and hoping know one uses the peep
hole).
I've confirmed function as best I can with and without http turned on and with
and without clientAuth. It appears to be working correctly.
> THe httpsPort flag starts another http thread not an https thread
> -----------------------------------------------------------------
>
> Key: MTOMCAT-108
> URL: https://issues.apache.org/jira/browse/MTOMCAT-108
> Project: Apache Tomcat Maven Plugin
> Issue Type: Bug
> Components: tomcat7
> Affects Versions: 2.0
> Environment: MAc OSX 10.6.8
> Reporter: Keith Corbin
> Assignee: Olivier Lamy
> Attachments: https.patch
>
>
> WHen you run the executable war the httpsPort flag starts an http protocol
> listener thread on the port listed not an https protocol listener.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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
