ADSS Signing Server
Verification was un-successful:
An error has occurred whilst verifying the document, possible reasons include:
* The file may not be a valid PKCS#7 object
* The file may not contain any PKCS#7 signatures
If you have supplied your own file then our support team can check that it is compatible by sending it (zipped please) to firstname.lastname@example.org with a short note explaining that an error occurred while verifying PKCS#7 signatures within the Ascertia website demo system.
- Server-side verification uses a flexible
OASIS DSS API that can define how ADSS Server should verify the signature and
what evidence information should be returned, e.g. CRL/OCSP revocation
information, certificate path information, etc.
- Using the Verification Service API, the
client application can request the Verification Service to return a range of
information about the signer, the issuing Certification Authority or the
information gathered as part of the verification process. This includes CRLs,
OCSP responses, timestamps, Quality information, certificate extension
- All verification service responses are
signed by the Ascertia ADSS Verification Server so that clients can see that these are
genuine messages from a trusted authority and they have not been changed.
- The ADSS Verification Server not
only ensures that the document has not been changed since signing and that the
signer’s credentials are valid (not expired, not revoked and issued by a trusted
CA) but can also report on the quality level of the signature and the associated
certificate quality level – see this information on