We have experienced the following error messages appearing in our log files when attempting to run our development module with Oracle Java versions 17 & 17.0.4.
Eventually, the module fails to start as a result of these failures.
Caused by: java.security.NoSuchAlgorithmException: Cannot find any provider supporting AES/GCM/NoPadding
at javax.crypto.Cipher.getInstance(Cipher.java:571) ~[?:?]
at com.bmc.ctm.security.algorithms.AbstractJceSecureAlgorithm.getCipherInstance(AbstractJceSecureAlgorithm.java:34) ~[bmc-security-2.2.jar!/:?]
at com.bmc.ctm.security.algorithms.JceAESGCMSecureAlgorithm.decrypt(JceAESGCMSecureAlgorithm.java:93) ~[bmc-security-2.2.jar!/:?]
at com.bmc.ctm.security.JCESymmetricKeyManager.decrypt(JCESymmetricKeyManager.java:188) ~[bmc-security-2.2.jar!/:?]
at com.bmc.ctm.mft.util.encryptor.EncryptorStrategy$AESGCM_Encryptor.doDecrypt(EncryptorStrategy.java:114) ~[mft-util-9.2100.jar!/:?]
... 41 more
From our java.security file:
security.provider.1=BCFIPS C:HYBRID;DEFRND[SHA256];ENABLE{ALL};
security.provider.2=BCJSSE
security.provider.3=SUN
security.provider.4=SunEC
When working with the original java.security file (not listing the BC providers within the providers list), the module starts successfully without any error messages.
We have not experienced this issue while working with Eclipse Adoptium Temurin & Azul Zulu Javas version 17.0.4.
Are you familiar with any issues while working with BC and Oracle Java 17?