We hit issue on JBossWS testsuite in WS security tests on JDK8. When we add BouncyCastle security provider in java.security file as last provider, the exception is thrown with root case: Original Exception was java.security.InvalidAlgorithmParameterException: Unsupported parameter: javax.crypto.spec.IvParameterSpec@63da70df at org.apache.xml.security.encryption.XMLCipher.decryptToByteArray(XMLCipher.java:1764) at org.apache.xml.security.encryption.XMLCipher.decryptElement(XMLCipher.java:1618) at org.apache.xml.security.encryption.XMLCipher.decryptElementContent(XMLCipher.java:1656) at org.apache.xml.security.encryption.XMLCipher.doFinal(XMLCipher.java:978) at org.apache.ws.security.processor.ReferenceListProcessor.decryptEncryptedData(ReferenceListProcessor.java:337) ... 33 more Caused by: java.security.InvalidAlgorithmParameterException: Unsupported parameter: javax.crypto.spec.IvParameterSpec@63da70df at com.sun.crypto.provider.CipherCore.init(CipherCore.java:509) [sunjce_provider.jar:1.8.0] at com.sun.crypto.provider.AESCipher.engineInit(AESCipher.java:339) [sunjce_provider.jar:1.8.0] at javax.crypto.Cipher.init(Cipher.java:1368) [jce.jar:1.8.0] at javax.crypto.Cipher.init(Cipher.java:1301) [jce.jar:1.8.0] at org.apache.xml.security.encryption.XMLCipher.decryptToByteArray(XMLCipher.java:1760) ... 37 more which is related to https://issues.apache.org/jira/browse/SANTUARIO-392, in short The issue is fixed in santuario 1.5.7
Checked with 6.4.0.DR2 which contains santuario 1.5.7 and issues on JDK8 are gone (tested with BouncyCastle 1.51).
Verified with 6.4.0.DR2 during 6.4.0.DR5 testing cycle.