[
https://issues.jboss.org/browse/WFLY-1094?page=com.atlassian.jira.plugin....
]
Hauke Mehrtens commented on WFLY-1094:
--------------------------------------
Some of our costumers are using JBoss EAP and our application needs the TLS cipher suite
TLS_RSA_PSK_WITH_AES_128_CBC_SHA, which we implemented in an own security provider. This
special TLS cipher suite is only used for a special dedicated connection and the
application server has to talk "normal" ssl on other ports at the same time.
Currently we patched the source code of the corresponding community edition and replaced
the jboss-web jar with our patched jar in the community and EAP version.
Use own JSSE Provider for http Connector
----------------------------------------
Key: WFLY-1094
URL:
https://issues.jboss.org/browse/WFLY-1094
Project: WildFly
Issue Type: Feature Request
Components: Web (JBoss Web)
Affects Versions: 8.0.0.Alpha1
Reporter: Hauke Mehrtens
Assignee: Tomaz Cerar
Labels: https, jsse, ssl
Attachments: ssl-protocol.patch
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:
{code:xml}
<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>
{code}
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