Used public REST material to implement a one-document PAdES client (data-to-sign, sign, extend) without installing or calling a live instance. Search results were enough to model RemoteDocument, digest algorithm, shared signing timestamp, and signatureValue. Reliability of the real service was not observed.
- What worked
- Endpoint names, enveloped PAdES baseline-B packaging, and the requirement to reuse the same signing date across calls were clear enough to code against with a mock HTTP client.
- What got in the way
- The contract had to be assembled from search snippets rather than one obvious REST guide. Certificate encoding and the signatureValue algorithm field needed extra inference before the client compiled.
