.png){kind=logo}
SignServer supports multiple interfaces for integration, but not all Workers can be called through all interfaces. Some Workers require that requests go through specific interfaces, endpoints, or operations.
Available client interfaces:
The table lists the interfaces supported by each Worker, with the following indicators:
Interface not intended?
Some workers are designed to sign complex file formats, such as JAR files, Windows executables, or APK packages, where the signing process involves more than just computing a signature. These workers require specific preparation of the file before signing and must embed the resulting signature back into the file in a format-specific way.
Examples:
-
Signing MS Authenticode files using MS Authenticode CMS Signer
-
Signing JAR files using JArchive CMS Signer
The SignServer SignClient interface is purpose-built to handle this preparation and embedding logic. If using other interfaces directly, you need to implement logic to match the request and responses of these signers, if supported. Therefore, these workers show a warning
|
Worker |
REST |
SignClient |
Client Web |
Client WS |
HTTP |
|---|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|