Free Support Forum - aspose.com

Aspose jar signed with an expired certificate

Hello,

After an update on apose.words.jasperreports from aspose.words.jasperreports-19.7.jar to aspose.words.jasperreports-7.1.0-7.2.0-19.10.jar, the following exception was raised

image.png (12.2 KB)

An analysis on signed classes pointed out that the apose.words.jasperreports-19.7 was signed with a valid certificate ( entry signed on 09/08/19 and certificate valid from 15/07/16 02:00 to 15/10/19 01:59) but the same class on the last release (entry signed on 31/10/19) was signed with the same certificate expired on 15/10/19.
Could you please signed the jar with a valid certificate in order to unlock the situation ?
Thanks for your help.

More informations

Entry from aspose.words.jasperreports-19.7.jar

sm 11897 Fri Aug 09 09:22:18 CEST 2019 com/aspose/words/awjr238.class

  [entry was signed on 09/08/19 08:22]
  X.509, CN=Aspose Pty Ltd, O=Aspose Pty Ltd, L=Lane Cove, ST=New South Wales, C=AU
  [certificate is valid from 15/07/16 02:00 to 15/10/19 01:59]
  X.509, CN=Symantec Class 3 SHA256 Code Signing CA, OU=Symantec Trust Network, O=Symantec Corporation, C=US
  [certificate is valid from 10/12/13 01:00 to 10/12/23 00:59]
  X.509, CN=VeriSign Class 3 Public Primary Certification Authority - G5, OU="(c) 2006 VeriSign, Inc. - For authorized use only", OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US
  [certificate is valid from 08/11/06 01:00 to 17/07/36 01:59]

Entry from aspose.words.jasperreports-7.1.0-7.2.0-19.10.jar

m 1125 Thu Oct 31 12:24:10 CET 2019 com/aspose/words/awjr238.class

  [entry was signed on 31/10/19 10:24]
  X.509, CN=Aspose Pty Ltd, O=Aspose Pty Ltd, L=Lane Cove, ST=New South Wales, C=AU
  [certificate expired on 15/10/19 01:59]
  X.509, CN=Symantec Class 3 SHA256 Code Signing CA, OU=Symantec Trust Network, O=Symantec Corporation, C=US
  [certificate is valid from 10/12/13 01:00 to 10/12/23 00:59]
  X.509, CN=VeriSign Class 3 Public Primary Certification Authority - G5, OU="(c) 2006 VeriSign, Inc. - For authorized use only", OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US
  [certificate is valid from 08/11/06 01:00 to 17/07/36 01:59]

@gsalmon

Could you please share the complete steps that you are using to reproduce this issue at our end? If you face this issue while exporting your report, please ZIP and attach the .jrprint file here for testing. We will investigate the issue and provide you more information on it.

Hello Tahir,

This exception occurs when registering the license when starting the application. Please find below the line from where the exception is raised (line 157).

image.png (3.0 KB)

Given the exception, it makes me think that we have 2 classes having the same package with different signature. I’m trying to investigate on my side too.

@gsalmon

We have tested the scenario using the latest version of Aspose.Words for JasperReports 19.10 and have not found the shared issue. Please remove all old references of Aspose.Words for JasperReports, clean you application and add the reference to the latest version.

A post was split to a new topic: java.lang.SecurityException is thrown when Aspose.Words for Java and Aspose.Words for JasperReports are used in same application

@gsalmon

After further investigation, we have noticed that java.lang.SecurityException is thrown when Aspose.Words for Java 19.11 and Aspose.Words for JasperReports 19.10 are used in same application.

For the sake of correction, we have logged this problem in our issue tracking system as WORDSJR-278. You will be notified via this forum thread once this issue is resolved.

We apologize for your inconvenience.