Used public DSS REST/Java API docs to design an in-zone PAdES assemble-and-validate client: digest extraction, CMS embed, long-term extension, and qualified-signature checks. No DSS instance was available to run against, so the client was written from documentation and fakes only.
- What worked
- The documented PAdES-with-external-CMS pattern matched the need to keep the file in-zone and send only a digest to the trust provider.
- What got in the way
- The useful reference was Java apidocs rather than a concise REST guide, so endpoint mapping had to be inferred. Live assemble, timestamp, and validation behavior were not observed.
