Issue with Signature Validation After Upgrade to WebViewer 11.6.0

Technical Support
, , ,
21

Hi Rahul,

Thank you for reaching out. I apologise for the delay.

We are still looking into this. I will let you know when there is an update.

Best Regards,
Mickaël.

1 Like
22

Hi Rahul,

Our product team confirms the issue and will work to resolve this.

We will let you know when there is an update.

Best Regards,
Mickaël.

1 Like
23

Hi Mickael,

Thank you for the update. As we are facing this issue in production, could you please let us know which build we can expect the fix to be included in?

Thanks,

Rahul Y

1 Like
24

Hi Rahul,

The issue is still under review, and there is no planning as of now.

Best Regards,
Mickaël.

1 Like
25

Hi Mickael,

Thank you for the update.

We would like to express our serious concern regarding this issue. As we have already paid the full API license fee, it is quite disappointing that this problem has been impacting our production environment for the past two months with no clear timeline or plan for resolution.

This issue is directly affecting our operations, and we were expecting timely support as part of the licensed service. We kindly request that this matter be treated on a priority basis and that we receive a concrete update or action plan at the earliest.

Looking forward to your prompt response.

Best Regards,
Rahul

1 Like
26

Hi Rahul,

We completely understand, and I can guarantee you that we are still investigating your issue.

We believe your issue might come from a regression made in version 11.6.0.
This was handled in 11.6.1:

Have you tried upgrading to 11.6.1 or more to see if that resolves your issue?

Best Regards,
Mickaël.

1 Like
27

Hi,

Yes. Already told you that we are facing this issue in 11.8.0 as well.

Thanks,

Rahul Y

1 Like
28

HI,

Any Update?

Thanks,

Rahul Y

1 Like
29

Hi Rahul,

I’ve reached out internally and will get back to you as soon as I have an update.

Best Regards,
Mickaël.

1 Like
30

Hello @rahul.tech8 ,

Thank you for your patience.

Our development team has been working on improving workflows regarding multiple digital signatures, and have introduced the “annotationManager.sign” API in our latest release (Version 11.12) to help with this workflow to ensure that existing signatures will not be flagged invalid by Adobe as reported.

You can see the specific changelog here: https://docs.apryse.com/web/guides/changelog

See our updated guide with new code snippets for signing documents: https://docs.apryse.com/web/guides/signature/sign-pdf

Let us know if this works for you!

Best Regards,
Jacob Romano Carlsen
Web Development Support Engineer
Apryse Software Inc.

1 Like
31

Hello,

Thank you for sharing the update and the documentation links.

I’ve gone through the changelog and the updated guide for the new annotationManager.sign API introduced in version 11.12. I understand that this new approach changes the implementation for applying digital signatures.

In my current implementation, I include additional details such as location, contact information, and reason while applying the digital signature. However, in the new method, I’m not seeing how these fields can be passed or configured.

Could you please guide me on how to include these properties (location, contact info, and reason) using the new API? If there is an alternative approach or additional configuration required, I would appreciate an example.

Best regards,
Rahul

34

Just following up on my earlier question—could you please confirm how to include location, contact info, and reason using the new annotationManager.sign API?

1 Like
35

The annotationManager.sign API is a new convenience API that is not meant to handle all possible situations.

For full signing features you would have to drop down a level of abstraction to our PDFNet “Core” API. Here is a sample showing some of the interactions.

Though the sample above is not integrated with WebViewer, so at least a few more lines would be needed to interact with WebViewer.

Before you go down this path though we are reviewing the feasibility of adding the options you ask about to this new sign API. I would recommend giving us a bit more time to let you know, unless you are in big rush, then we can work on migrating you.

36

Hi,

Currently, I am using the PDFNet “Core” API for signing features. However, I am encountering some issues with multiple signatures, as mentioned earlier in this thread.

It would be very helpful if you could include options such as location, contact information, and reason within the new annotationManager.sign API. This would allow me to rely on the higher-level API instead of working directly with the Core API.

I would appreciate it if you could prioritize this, as I have been waiting for this functionality for some time.

Thank you.

1 Like
37

Thank you for the clarification, this has been passed on.

The team plans to add this ability, but I don’t have a concrete schedule, but I believe at least a couple of months out still.

1 Like
38

Hi,

Any update on it?

1 Like
39

Our engineering team is still investigating this, but have established a plan to address the issue.

1 Like