Integration
Communication
In SIGNIUS Sealing Client we have two available ways of communication:
FILESYSTEM
REST API
Both of these are dependent on the SIGNIUS Sealing Server configuration in particular the "process" configuration
FILESYSTEM
Each "process" is programmed for one type of sealing/signing (PAdES/XAdES/CAdES/etc.). When "process" is configured on server side and SIGNIUS Sealing Client is restarted, it creates directory with three hardcoded subfolders "in", "out" and "err".
When document sealing/signing is required, simply put (copy or move) file into "in" subfolder and a moment later the file will disappear and reappear already signed in the "out" subfolder. If however something unexpected happened that prevented document sealing/signing, it will appear in the "err" folder unsigned.
Supports both local and network directories (UNC path format)
REST API
Details on the REST API communication are available at (links below):
Last updated