[
https://issues.jboss.org/browse/WFLY-10945?page=com.atlassian.jira.plugin...
]
David Lloyd commented on WFLY-10945:
------------------------------------
JDK 9 will load providers from the boot module or JAR with service loader. But that does
not apply here. JBoss Modules will also load providers from the boot module given to it,
so if this module is part of the boot module set, it will be loaded and installed.
Finally, Elytron's authentication components have the capability to locate providers
at run time via service loader, but without installing them globally. Whether this is
done depends on configuration and also on what our defaults are (which I do not recall),
and also (obviously) on whether the provider module is visible to the class loader on
behalf of whom the service loading is being done.
JDK11 ws testsuite SSL failures
-------------------------------
Key: WFLY-10945
URL:
https://issues.jboss.org/browse/WFLY-10945
Project: WildFly
Issue Type: Sub-task
Components: Test Suite
Affects Versions: 14.0.0.Beta2
Reporter: Jan Kalina
Assignee: Jan Kalina
Priority: Blocker
Fix For: 15.0.0.Alpha1
ws testsuite failures on JDK-11:
* missing local IP in SubjectAlternativeNamesExtension
* TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 + TLS1.2 seems buggy on JDK-11: Invalid ECDH
ServerKeyExchange signature
* not issue after switching to TLS1.1 or to ciphersuite TLS_RSA_WITH_AES_256_CBC_SHA256
-> JDK bug
--
This message was sent by Atlassian Jira
(v7.12.1#712002)