-
Bug
-
Resolution: Done
-
Major
-
1.6.0.Final
-
None
Check Trace logging of ssl context creation. How I read code logging should apply after throw expression. That wouldn never happen. Also there is another throw of exception with SSLUtils::throwIt.
org.wildfly.security.ssl.SSLUtils
// now return a factory that will return the best match is can create. final String[] supportedProtocols = protocolSelector.evaluate(preferredProviderByAlgorithm.keySet().toArray(NO_STRINGS)); if (supportedProtocols.length > 0) { return () -> { for (String protocol : supportedProtocols) { List<Provider> providerList = preferredProviderByAlgorithm.getOrDefault(protocol, Collections.emptyList()); for (Provider provider : providerList) { try { return SSLContext.getInstance(protocol, provider); } catch (NoSuchAlgorithmException ignored) {} } } throw ElytronMessages.log.noAlgorithmForSslProtocol(); }; } if (log.isTraceEnabled()) { log.tracef("No %s provided by providers in %s: %s", SERVICE_TYPE, SSLUtils.class.getSimpleName(), Arrays.toString(providerSupplier.get())); } return SSLUtils::throwIt;
- is cloned by
-
JBEAP-15436 Trace logging in SSLUtils
- Closed
- relates to
-
ELY-1663 BC FIPS, Management Interface, ELY04001: No algorithm found matching TLS/SSL protocol selection criteria
- Resolved