[jboss-jira] [JBoss JIRA] (AS7-6087) CLONE - Use own JSSE Provider for http Connector

[Tom Fonteyne (JIRA)]

Tom Fonteyne created AS7-6087:
---------------------------------

             Summary: CLONE - Use own JSSE Provider for http Connector
                 Key: AS7-6087
                 URL: https://issues.jboss.org/browse/AS7-6087
             Project: Application Server 7
          Issue Type: Feature Request
          Components: Web
    Affects Versions: 7.1.2.Final (EAP)
            Reporter: Tom Fonteyne
            Assignee: Remy Maucherat


We are using our own JSSE Provider implementation for TLS to add support for HTTPS with preshared key to one http connector, while the others still use the default JSSE provider.

In JBoss 5 we added sslProtocol="RFC4279", while RFC4279 is the name of our provider, to one Connector entry in the file server/default/deploy/jbossweb.sar/server.xml. This option is not available in JBoss 7.1 any more and we could not find a way to make one connector use our provider while the others are using the default one.

To fix this issue for use we used the attached patch. We would like to get this patch into the next version of JBoss, so we do not have to modify the source code by our self any more. This patch was tested with JBoss 7.1.2, but it still applies against the master branch. If we should do any changed to the patch or if you want to get it in an other form please inform us.

With this patch we are able to specify our JSSE provider like this:

<connector name="httpspsk" protocol="HTTP/1.1" scheme="https" socket-binding="httpspsk" secure="true">
  <ssl name="ssl" key-alias="intended purpose ssl test from bremen online services" password="123456" certificate-key-file="${jboss.server.config.dir}/governikus_ssl.jks" protocol="ALL" keystore-type="JKS" ssl_protocol="RFC4279"/>
</connector>

This is related to Red Hat Customer Portal support case 00721624 "Additional JSSE Provider on socket bindings and connectors"

--
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