[
https://issues.jboss.org/browse/WFCORE-1802?page=com.atlassian.jira.plugi...
]
Darran Lofthouse commented on WFCORE-1802:
------------------------------------------
I am undecided ;-)
The Elytron Subsystem now discovers and registers the Provider so we should be able to
remove it from the current location.
We probably should encourage the use of the Elytron subsystem for SSLContext definitions
and both Elytron and the OpenSSL integration are new in WildFly 11.
BUT attempting to use the OpenSSL provider in legacy resources could then become racey as
the legacy services don't depend on the core Elytron services by default.
Integrate OpenSSL Provider registration with Elytron
----------------------------------------------------
Key: WFCORE-1802
URL:
https://issues.jboss.org/browse/WFCORE-1802
Project: WildFly Core
Issue Type: Task
Components: Security
Reporter: Stuart Douglas
Assignee: Darran Lofthouse
Priority: Blocker
Fix For: 3.0.0.Alpha23
We need to remove the following block from SecurityRealmResourceDefinition: -
{code}
static {
//register the Openssl Provider, if possible
//not really sure if this is the best place for it
try {
OpenSSLProvider.register();
DomainManagementLogger.ROOT_LOGGER.registeredOpenSSLProvider();
} catch (Throwable t){
DomainManagementLogger.ROOT_LOGGER.debugf(t, "Failed to register OpenSSL
provider");
}
}
{code}
Registration will then be possible within the Elytron subsystem configuration.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)