Failed to sign PDF files using certificate from Window Certificate Store if we check 'Enable strong private key protection'

Hi Aspose team,

We are using Aspose.pdf.dll v19.2 for signing pdf files.
If we check ‘Enable strong private key protection’ when we install the certificate to Windows Certificate Store, and then we choose this certificate from Window Certificate Store while signing a PDF file, there is an exception occurs.
image.png (20.2 KB)
Here’s the demo code, test pdf files and certificate.
https://drive.google.com/file/d/1Rw6pGEy3lgnXzUyb92ZUBHYY6qVL4hu9/view?usp=sharing

@Glority_Developer

We were able to observe the exception in our environment while testing the scenario using Aspose.PDF for .NET 20.7. Therefore, we have logged it as PDFNET-48544 in our issue tracking system. We will surely check this in details and keep you posted with its resolution status. Please be patient and spare us some time.

We are sorry for the inconvenience.

Hi Aspose team,

Is there any progress on it?

@Glority_Developer

We are afraid that earlier logged ticket is not yet resolved due to other issues in queue logged prior to it. However, we will surely inform you as soon as the ticket is investigated and we have some news about its resolution ETA. Please spare us some time.

We apologize for your inconvenience.

Hi Aspose team,

Would you please check if it’s solved? Thank you.

@Glority_Developer

We regret to inform you that the earlier logged ticket could not get resolved yet. We have recorded your concerns and will surely consider them during the issue investigation. Please be patient and give us some time.

We apologize for the inconvenience caused.

Hi Aspose team,

Did you have any progress on it? We are going to have the code freeze date of our product. Will this issue be fixed within 1-2 months?

@Glority_Developer

We would like to share with you that your issue has been resolved in 21.7 version of the API which will be released next month. You will be notified in this forum thread as soon as the fix-in version in published.

The issues you have found earlier (filed as PDFNET-48544) have been fixed in Aspose.PDF for .NET 21.7.