Can you explain more on what you want from "Binding"?
What is your protection profile for your signature solution?
Could you just match keys and then allow the signature? Is logging in good enough to identify the user?
In other words, could a user login and then sign with iPad? You predetermin who must sign and then you match their login credentials (what they know) to the predetermined person. They would need to do this for every document/record they need to sign.
Hi Zorba: In simple terms, "binding" means coming up with something like a numeric signature for the data in the document and combining that in some form with a numeric signature for the signature and combining them somehow so that if the process is repeated, you always get the same value. If the value is ever different, then you know the document was modified.
As far as how it is signed, logging in and then using a "pin" to sign the document would work just fine.
This process is both about attesting to the truth of the document as well as being able to prove it is not modified.
I hope this answers your question.
Check out what the guys at Docusign are doing. It's not FM, but should give you a better idea what you need to do.
Filemaker has no built-in method to generate a digitally signed PDF (or other type of) document. That means you'll need to use either a plugin or a system-level script to accomplish the task.
I know there is an e-sign solution from PCI that involves capturing a biometric signature
A link would be useful - at least to know what kind of security you are aiming at. See also:
I should add that this problem could be broken into two, where the first part would be verifying that the signatory is who they say they are. This part could definitely be performed within Filemaker, by forcing the user to relogin. However, it raises the question of storing the users' digital signature credentials in your solution - something I would be extremely averse to.