Changes introduced by JDK-6311046 resulted in failures in many JCK api/javax_crypto tests. BaddPaddingExceptions and InvalidKeyExceptions are thrown with the same message of "Invalid pad value". The failure occurs only with SunPKCS11 provider, which is default on Solaris installs. It can occur on other OSes if SunPKCS11 is enabled.

java.security.InvalidKeyException: Invalid pad value!
        at javax.crypto.SealedObject.getObject(SealedObject.java:355)
        at javasoft.sqe.tests.api.javax.crypto.SealedObject.getObject4Tests.getObject4Tests0001(getObject4Tests.java:125)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        ...


The following tests that threw exceptions causing a failure are:
api/javax_crypto/Cipher/index_doFinal1Tests
api/javax_crypto/Cipher/index_doFinal2Tests
api/javax_crypto/Cipher/index_doFinal3Tests
api/javax_crypto/Cipher/index_doFinal4Tests
api/javax_crypto/Cipher/index_init1Tests
api/javax_crypto/Cipher/index_init2Tests
api/javax_crypto/Cipher/index_update1Tests
api/javax_crypto/Cipher/index_update2Tests
api/javax_crypto/CipherInputStream/index2_read5
api/javax_crypto/CipherInputStream/index_read1Tests
api/javax_crypto/CipherInputStream/index_read2Tests
api/javax_crypto/CipherInputStream/index_read3Tests
api/javax_crypto/CipherOutputStream/index_flushTests
api/javax_crypto/CipherOutputStream/index_write1Tests
api/javax_crypto/CipherOutputStream/index_write2Tests
api/javax_crypto/CipherOutputStream/index_write3Tests
api/javax_crypto/SealedObject/index2_getObject4
api/javax_crypto/SealedObject/index_getObject1Tests
api/javax_crypto/SealedObject/index_getObject2Tests
api/javax_crypto/SealedObject/index_getObject3Tests