Recently working with the Zulu JDK we realised our use of ServiceLoader discovery is loading both the services defined in META-INT/services and those defined in the JPMS of the JDK.
The issue MODULES-402 is adding an API to JBoss Modules to allow filtering before Providers are instantiated and WFCORE-5185 is to look at filtering in the Elytron subsystem.
This issue is to look at the options in the following class:
org.wildfly.security.provider.util.ProviderServiceLoaderSupplier
In the subsystem we know we are in a modular environment so can check the type of the ClassLoader but for ProviderServiceLoaderSupplier we may be in a client not using JBoss Modules so may need to review alternative filtering strategies. In the client it is even more likely that JPMS definitions may be desirable so this will need to be considered further.
- clones
-
ELY-2040 ServiceLoader discovery of security Providers discovers JDK instances as well
- Open
- is blocked by
-
JBEAP-20501 (7.3.z) MODULES-402 - Introduce utility method like <T> Iterable<T> Module.findServices(Class<T> type, Predicate<Class<?>> filter)
- Closed
- is related to
-
JBEAP-20503 [GSS](7.3.z) WFCORE-5185 - Update ProviderDefinition to use optimised service loading API
- Closed