Bouncy castle -jdk15on is not maintained anymore., instead -jdk18on should be used.
The issue here is, introducing any other BC variant into the classpath causes major breakage,
Exceptions like Could not initialize class org.bouncycastle.cms.CMSSignedData happen. Apparently some bouncy-castle-internal algorithm identifiers and/or SPI wirings have changed and BC tries to load algorithm combinations, which do not exist, like sphincs with sha2, for example.
An switch/update to bcpkix-jdk18on should fix everything.
Bouncy castle -jdk15on is not maintained anymore., instead -jdk18on should be used.
The issue here is, introducing any other BC variant into the classpath causes major breakage, Exceptions like
Could not initialize class org.bouncycastle.cms.CMSSignedDatahappen. Apparently some bouncy-castle-internal algorithm identifiers and/or SPI wirings have changed and BC tries to load algorithm combinations, which do not exist, like sphincs with sha2, for example.An switch/update to bcpkix-jdk18on should fix everything.