ADSS Signing Server
verification of signed XML documents
You can verify any signed XML document in
this demo. The Ascertia ADSS demo Verification Server has a list of Certificate
Authorities (CAs) trusted to issue certificates to end-users
as listed here. Only if your document is signed using a credential
from one of these CAs it will be shown as trusted. The ADSS Verification
Server can support an unlimited number of CAs each with their
own validation policy.
- 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.
- All verification service responses are signed by the 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
- If you are uploading a document we restrict the file size to
and documents having 50 pages or less – just for this demo.