Error in image conversion

Aspose.Imaging Product Family
, ,
1

We have renewed and applied the Aspose licenses in Feb 2025. However we started seeing the image conversion issues around 2nd week of March. Below are the jar files used for conversion. Do you see any problem because of these?
Error Message : class com.aspose.imaging.coreexceptions.FrameworkException: Failed to set license. Details: Signature encoding error

image.png (34.3 KB)

2

@yogeshnemade

Could you please provide more details about the specific image conversion issues you are encountering? Additionally, please share the code you are using for the conversion.

3

Hello @yogeshnemade
We appreciate that you use Aspose.Imaging.
Yes, unfortunately, a new license format is not supported by old versions of the library.

4

Thank you @evgeniy.sidenko .
We have renewed the license in Feb 2025 and issue started around in March. So not sure if its the license compatibility issue or something else. Is there any way we can check the encryption(SHA1 or sha256) of this license and the previous license?

5

The old version of the license was based on SHA1, and the new one on SHA256.
You can check the encryption this way

  1. Take a signature value () as a string
  2. Using Base64.decode convert it into a byte array
  3. If the byte array length == 128 then it is SHA1, length == 256 then it is SHA256
6

Hi @evgeniy.sidenko
This helped. I see its 256. One thing thats bothering is we applied the cert in Feb and started seeing the issue in March. We see error message as below. Do you think its because of this new licensing?

c.g.p.b.impl.AsposeDocumentProvider : Failed to set license. Details: Signature encoding error
c.g.p.b.impl.AsposeDocumentProvider : exception ocoured while converting document
class com.aspose.imaging.coreexceptions.FrameworkException: Failed to set license. Details: Signature encoding error

7

Hi, @yogeshnemade
As I can see from the picture, you use Aspose.Imaging for Java 20.7. It is a very old library that supports only SHA1 signatures. That is why it throws the exception “Signature encoding error” because it considers SHA256 a broken signature.

8

Ohh Ok .

Is there a way or documentation which will guide us on the impact of using the latest libraries in our code?

9

As far as I am aware, there is no such guide available. It seems that if you do not inherit from the Image or RasterImage classes, there is no side effect.
You might analyze the release notes here

or here