- This line was added.
- This line was removed.
- Formatting was changed.
If you want to take a look at the source code of a webapp displaying individual and bulk signature integration with Blobfish Signer immediately, download blobfish-signer-webapp-1.0-SNAPSHOT-src.zip from Downloads.
See Individual signature integration for detailed instructions that you could find useful applying the current instructions.
To perform bulk signature you need to review the following steps.
1. Prepare signature entries
In this step you need to prepare the entries to be signed as comma separated values (CSV) with the following structure, and provide them from a URL:
<downloadURL1>,<uploadURL1>,<documentName1> <downloadURL2>,<uploadURL2>,<documentName2> <downloadURL3>,<uploadURL3>,<documentName3> ...
A simple example would be placing the following content in a static file:
And place it in your web app content root, for example:
It is worth noting that in real life the CSV entries wouldn't be usually served by a static file as in the example shown, but instead they would be produced dynamically by the web app in response to a HTTP
The CSV is expected to be in RFC 4180 format, but empty lines will be ignored. For reference, this is the implementation Blobfish Signer uses for parsing the provided CSV: https://commons.apache.org/proper/commons-csv/apidocs/org/apache/commons/csv/CSVFormat.html#DEFAULT.
Note that Blobfish Signer currently always expect the provided CSV to be UTF-8 encoded.
2. Compose "bsign" hyperlink
After having ready the signature entries URL, you need to create a bsign hyperlink as follows, where
signatureEntriesURL needs to be URL encoded (percent-encoded):
<a href="bsign:?batch_csv=<signatureEntriesURL>">Bulk sign</a>
For our example the result would be:
<a href="bsign:?batch_csv=http%3A%2F%2Fexample.org%2Fsample-app%2Fsignature_entries.csv">Bulk sign</a>
On this page: