[ https://issues.jboss.org/browse/WFLY-10945?page=com.atlassian.jira.plugin... ] Martin Choma edited comment on WFLY-10945 at 10/8/18 12:41 PM: --------------------------------------------------------------- Looking into modules/system/layers/base/org/bouncycastle/main and I see * META-INF/services/java.security.Provider defined in bcprov-jdk15on-1.60.0.redhat-00001.jar * this snippet in module.xml {noformat} <provides> <service name="java.security.Provider"> <with-class name="org.bouncycastle.jce.provider.BouncyCastleProvider"/> <with-class name="org.bouncycastle.pqc.jcajce.provider.BouncyCastlePQCProvider"/> </service> </provides> {noformat} That mean BouncyCastle is registered in JDK9+ automatically on server. BecauseIn JDK9+ providers started to be loaded also with service loader mechanism. [~dmlloyd] Do I recall correctly? was (Author: mchoma): Looking into modules/system/layers/base/org/bouncycastle/main and I see * META-INF/services/java.security.Provider defined in bcprov-jdk15on-1.60.0.redhat-00001.jar * this snippet in module.xml {noformat} <provides> <service name="java.security.Provider"> <with-class name="org.bouncycastle.jce.provider.BouncyCastleProvider"/> <with-class name="org.bouncycastle.pqc.jcajce.provider.BouncyCastlePQCProvider"/> </service> </provides> {noformat} That mean BouncyCastle is registered in JDK9+ automatically on server. BecauseIn JDK9+ providers started to be loaded also with service loader mechanism. -- This message was sent by Atlassian Jira (v7.12.1#712002)