Why is .pfx file mandatory while e sign?

Aspose.PDF Cloud Product Family
1

I am trying to use aspose-pdf-cloud-node.js/test/testFields.ts at master · aspose-pdf-cloud/aspose-pdf-cloud-node.js · GitHub
to understand how e sign can be implemented. Let’s say I want to e-sign with name “test_user”. Then can’t I just set the rectangle coordinates, and sign can be placed at that place? why is signaturePath required? and considering my case, what should i do to generate it, if it is required?

Also, in above test case as well, I don’t understand where is this file “33226.p12”, coming from and what is its use?

2

@rajatdpw

Could you please clarify what specific issues you are facing with the e-sign implementation and the use of the .pfx file? Additionally, please provide more context about the ‘33226.p12’ file and its relevance to your implementation.

3

I already provided the reference link to github. I want to understand what pfx is required and why can’t i just provide the text and it should add that as signature?

PS: Also, can you explain what is meant by formFieldName and how should i create it?

4

@rajatdpw
You can read more about form fields in api reference Working with Form Fields|Documentation
In the part of the question about the signaturePath, this should be the path to the pfx file, previously uploaded to the cloud storage, the pfx file is necessary for signing the document and must contain the private key.