Thank you for further clarifications.
- The GroupDocs.Signature App Demo https://products.groupdocs.app/signature/total is an online demonstration of GroupDocs.Signature for .NET abilities and features. One of them is hand-made signature drawing as an example of your implementation. Near future we will provide the same functionality as you shared to enter text with special fonts to mimic the hand-written signature.
Besides that, the server side could be found below to do the same
There’s the ability to pass Text Signature and adjust it with additional options like Font, Size, Colors, Backgrounds, Effects etc.
So you may pass names like ‘John Smith’ with required Font etc to obtain Text Signature on the document. This signature can be generated as native text or like an image on a document page.
- Using Digital Certificates.
The server side library creates Digital Signatures for the documents using the PFX certificate files.
So the server-side part expects the PFX file/stream/bytes to be passed to the library (with the password of the private key).
At this moment the GroupDocs.Signature API product doesn’t support communication with exact devices due to a variety of SDK / specifications.
In your case the approach could be as follows.
- your server side code / front-end code accesses the HSM device to obtain the certificate. Please be aware that a digital certificate should be with a private/public key - this is the only way for proper digital signing. Having this certificate (as Stream/ bytes buffer / file) you pass it to the Signature library.
Having generated QR-Code as an image (in any format) you can pass it to the GroupDocs.Signature product as an Image signature object.
Besides that, GroupDocs.Signature for .Net/Java also can generate any QR-code.
So it’s easy to integrate your QR code images to the GroupDocs.Signature App
Rishikeshj, trying to help you with our product,
it seems that the main misunderstanding between your questions and my answers is related to basic principles using the Signature products.
This Demo contains Server Side (Back-end BE) that serves REST API communication with the Front-End UI part.
Server part implements low level document processing. Like adding signatures of various types to the document based on the passed options from Front-End UI.
So, the GroupDocs.Signature for .NET is a server side library that accepts document and signature options and returns output document (stream/file).
As an alternative solution we have GroupDocs Signature for Cloud - this is a REST-full API that can serve your Front-End application.
So summarize your questions, App is a demonstration of Signature for .NET/Java abilities.
There are following parts that will help you to build your solutions
GroupDocs.Signature for .NET/Java - server side solutions
GroupDocs Signature Cloud - document eSign REST API based solution
GroupDocs Signature Free App, front-end samples like GroupDocs.Signature for MVC - are demonstrations of how to use solutions from points 1 and 2.