PDF visual signatures are supported for both individual signature and bulk signature by receiving all the visual signature required parameters (five as explained later) from the web application that invokes Blobfish Signer. The existence of these parameters is entirely optional, i.e. if they are omitted, Blobfish Signer will generate invisible signatures.
Visual signature configuration is currently unsupported directly from the Blobfish Signer application. As previously indicated, the associated parameters have to be provided by the web application.
- Update "vis_sig_y" related documentation as its semantics are about to change in the 2.x releases.
Visual signature configuration for individual signature
First, take a look at Individual signature integration.
Basically, you need to provide the following highlighted five additional parameters.
The text to be displayed in the visual signature (
vis_sig_text) supports some placeholders that will be replaced at runtime as follows:
<SIGNER>: The digital certificate subject's common name attribute value or the full distinguished name if the common name attribute is not present.
<DATE>: The signing date in the following format:
dd/MM/yyyy HH:mm(see https://docs.oracle.com/javase/8/docs/api/java/text/SimpleDateFormat.html).
An example hyperlink would be:
vis_sig_text is the URL encoded (percent-encoded) representation for:
Visual signature configuration for bulk signature
First, take a look at Bulk signature integration.
As in "Visual signature configuration for individual signature" there are five additional parameters which should appear in the following order:
And a sample CSV with two signing entries would be the following one: