Command line interface for playing around with the DSS-Framework PDF Signature Validator settings.
The following parameters can be modified for single or multiple PDF documents:
- Validation policy
- Report output formats
- Build trust-store from DER encoded certificate files stored in a directory and/or database
The validation process is based on the DSS-Framework (https://github.com/esig/dss).
This Netbeans project can be build easily using Maven.
###Examples: Validate one document using default policy and an empty trust-store (the validation result will be invalid):
java -jar validator-cli-1.0-r<revision>.jar --file Document1.pdf
Validate multiple documents using own policy and trust-store from directory and database:
java -jar validator-cli-1.0-r<revision>.jar --file <path to directory containing PDFs> --certs <path to directory containing DER-Encoded certificates> --policy <path to policy-xml file> --database
Arguments:
-c,--certs directory containing certificates for validation. If no certificates are provided,no certificate is used for validation. -db,--database Certificates are loaded from the database specified in db.config.properties -f,--file The PDF file to validate. If a directory is provided, the application will search for documents and validate them. This argument is mandatory. -h,--help Shows this help dialog -l,--lotl Certificates are loaded from the LOTL specified in tsp.config.properties. IF THIS OPTION IS ACTIVE, THE FOLLOWING OPTIONS ARE IGNORED: --certs and --database -p,--policy DSS Validation Policy (XML Format). If not defined, the default policy is used. -rd,--rdest Destination for output file. If not defined, the output directory containing the PDF file is used. -rf,--rformat Report format. Multiple formats must be provided comma-separated without whitespace. Possible attributes: std (default), detail, diagnostic.