[
https://issues.jboss.org/browse/WFLY-1094?page=com.atlassian.jira.plugin....
]
David Lloyd commented on WFLY-1094:
-----------------------------------
The patch is not usable as-is because the management model has to remain compatible, thus
the schema rev has to be bumped up at a minimum.
When it comes to security providers, we should be allowing:
* Providers to be specified by provider name (search system class path)
* Providers to be specified by module name (use ServiceLoader on given module for the
first acceptable {{Provider}} of the right type)
* Providers to be specified by module name + provider name (use ServiceLoader on given
module for a {{Provider}} with the given ID)
* Providers to be specified by module name + class name (load the {{Provider}} subclass
directly by name and class loader)
This allows users to install alternative providers (e.g. BouncyCastle or whatever) as
modules. We *should* also provide some way to specify the security providers that are
available to deployments on a global and per-deployment basis.
Use own JSSE Provider for http Connector
----------------------------------------
Key: WFLY-1094
URL:
https://issues.jboss.org/browse/WFLY-1094
Project: WildFly
Issue Type: Feature Request
Reporter: Hauke Mehrtens
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