Aspose 24.4 jars: java.lang.SecurityException: class "com.aspose.pdf.internal.ms.System.I154"'s signer information does not match signer information of other classes in the same package

When I upgraded to Aspose 24.4 in Java, I got the following error:

java.lang.SecurityException: class “com.aspose.pdf.internal.ms.System.I154”'s signer information does not match signer information of other classes in the same package.

I have only the new jar files in my WEB-INF\lib folder when I generate the war file. Where I deploy my application, the old jars are on the classpath but I only include 24.4 jars in my project classpath and war deployment profile. Is it still finding the old jars despite only allowing for version 24.4? Is there a fix/workaround?

@jmmorgan

Please double-check that the old Aspose jar files are not being inadvertently included in the classpath of your application. Sometimes, libraries can be included in multiple places, such as the server’s classpath or the application server’s shared libraries. Also, if you can please share some steps with us to replicate the issue if our suggestion did help, we will generate an investigation ticket and share the ID with you.

There are old jars on the server classpath. However, removing those jars could break a lot of other applications on the server. Is there a workaround?

@jmmorgan

We are afraid that we cannot offer any workaround as we haven’t come across such issue before. If you can share some steps to replicate similar issue in our environment, we can register this case under an investigation ticket and share the ID with you.