Skip to content

Fortified IDDocs

Overview

Choose the DSS, CSC, organization seal or time stamp interface and the signing format appropriate to your application.

Choose the interface according to the signing operation and the role of the requester. Each instance runs one explicitly selected service mode.

Need Interface
A person approves document signing in the browser Document signing with a requesting system, using the signed DSS browser binding.
An application signs plain text or a text string Generic text signing, using detached CMS and the exact retained original bytes.
A CSC client obtains authorized signatures over document digests CSC signing, using the supported CSC API subset and separate OAuth/browser authorization.
The organization applies a seal without a human signer Organization seal, using a registered machine requester and organization profile.
A requester needs a trusted RFC 3161 time stamp Time stamping, using a configured external authority.

Signature formats describes XML, PDF, detached CMS, exact UTF-8 text, PAdES, XAdES and JAdES. All three AdES formats support consumer completion of B-B, B-T, B-LT and B-LTA, including archival renewal. The requesting system prepares inputs, retains originals and verifies the final result. Document format, a person's authentication and authority to use a signing key are separate concerns.

The Support service reference contains the DSS OpenAPI, XML contract and examples. CSC has its own OpenAPI and configuration schema. Optional External PKI and certificate issuance configures certificate supply; it does not replace the signer's authentication or consent and is separate from the time stamp service.