Signature exceptions

Thrown if a problem occurs when a credential is not found or the credential expired. The credential is required to sign or certify.

Thrown if a signature field is duplicated.

Thrown when FIPS compliance is not met. When FIPS is required, an FIPSComplianceException error is thrown when MD5 or RIPEMD160 is used as a digest hashing algorithm.

Thrown if an invalid argument that is required to perform a Signature operation is specified.

Thrown if the specified signature field cannot be located within a PDF document.

Thrown if the input PDF has no certifying signature and the operation requires one to be present.

Thrown if a specific operation cannot be performed on the input PDF document due to PDF-related processing errors.

Thrown if an operation is requested but the input PDF document has insufficient permissions to complete it.

Thrown at the time of signing or certifying if the seed values associated with the signature field cannot be validated.

Thrown if an attempt to sign a signature field failed.

Thrown if the specified signature field already contains a signature.

Thrown if a signature cannot be verified.

Thrown if an error occurs while digitally signing a PDF document.