Usage of ISO10126PADDING

We recently moved to FIPS certified Java Crypto Provider and our application is getting terminated because of usage of ISO10126PADDING. We are using 2.6.4 OpenSaml version.
Please let us know how we avoid this padding.

Error: -1 (NON_FIPS_CRYPTO_FEATURE): Process terminated due to its use of the non-FIPS cryptographic feature ISO10126PADDING

at java.base/javax.crypto.Cipher$Transform.setModePadding(Cipher.java:391)
at java.base/javax.crypto.Cipher.getInstance(Cipher.java:558)
at deployment.manage.war//org.apache.xml.security.encryption.XMLCipher.decryptToByteArray(XMLCipher.java:1780)
at deployment,manage.war//org.opensaml.xml.encryption.Decrypter.decryptDataToDOM(Decrypter.java:596)
at deployment.manage.war//org.opensaml.xml.encryption.Decrypter.decryptUsingResolvedEncryptedKey(Decrypter.java:795)
at deployment.manage.war//org.opensaml.xml.encryption.Decrypter.decryptDataToDOM(Decrypter.java:535)
at deployment.manage.war//org.opensaml.xml.encryption.Decrypter.decryptDataToList(Decrypter.java:453)
at deployment.manage.war//org.opensaml.xml.encryption.Decrypter.decryptData(Decrypter.java:414)
at deployment.manage.war//org.opensaml.saml2.encryption.Decrypter.decryptData(Decrypter.java:141)
at deployment.manage.war//org.opensaml.saml2.encryption.Decrypter.decrypt(Decrypter.java:69)

We are using AES-256 CBC. This breaks on Okta and works with PingID after minor changes to xmltooling 1.4.4. Where does Okta use the ISO10126 padding and is there a way to change it?

Any expert in this area. How do we avoid usage of ISO10126PADDING padding. Thanks