[
https://issues.jboss.org/browse/WFLY-4669?page=com.atlassian.jira.plugin....
]
Alessio Soldano resolved WFLY-4669.
-----------------------------------
Resolution: Out of Date
Hi,
the workaround in WFLY-3252 was extensively tested, so you'd need to provide a
description of the steps you used to reproduce the problem.
In any case, I'm solving this as out-of-date because it's not relevant anymore in
terms of webservices subsystem. Starting from WildFly 9, Bouncy Caste is not automatically
installed anymore (it's not required to be installed in the JDK), see the JBossWS 5
migration notes for further details
https://developer.jboss.org/wiki/JBossWS5MigrationNotes . As a consequence the workaround
from WFLY-3252 only deals with the scenario in which you manually install BC before the
webservices subsystem (or the whole server) is started; but in that case, you can control
where you put the provider.
BouncyCastle reorderProviders
-----------------------------
Key: WFLY-4669
URL:
https://issues.jboss.org/browse/WFLY-4669
Project: WildFly
Issue Type: Bug
Components: Web Services
Affects Versions: 8.2.0.Final
Environment: Linux, jdk 1.8.0.45
Reporter: Rafał Gołębiewski
Assignee: Alessio Soldano
Labels: bouncycastle, https,, webservi,
Fix for bug WFLY-3252 doesn't work, because BC provider is inserted at the position
of SunJCE provider. As jdk documentation says "The position is 1-based"
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)