- SignServer Introduction
- SignServer Installation
- SignServer Operations
- SignServer Integration
-
SignServer Reference
- Deploy-time Configuration
-
SignServer Workers
- Common Configuration
-
SignServer Signers
- Common Properties
- Time Stamp Signer
- MS Authenticode Time Stamp Signer
- Extended Time Stamp Signer
- MRTD Signer
- MRTD SOD Signer
- PDF Signer
- ODF Signer
- XML Signer
- XAdES Signer
- OOXML Signer
- CMS Signer
- Extended CMS Signer
- MS Authenticode Signer
- MS Authenticode CMS Signer
- JArchive Signer
- JArchive CMS Signer
- Master List Signer
- Plain Signer
- OpenPGP Signer
- Debian Dpkg-sig Signer
- OpenPGPPlain Signer
- SignServer Document Validators
- SignServer Dispatchers
- SignServer Validation Service Framework
- SignServer Timed Services
- Other Workers
- SignServer Components
- Logging
- SignServer Authentication and Authorization
- Status Repository
- Health Check
- SignServer TimeMonitor Application
-
SignServer User Interfaces
- Administration CLI
- Administration GUI
-
Administration Web
- Main Page
- Workers Page
- Global Configuration Page
- Administrators Page
- Audit Log Page
- Archive Page
- Database CLI
- Internationalization
- Peer Systems
- Client-Side Hashing
- Key Wrapping
- Developer Reference
- SignServer Release Information
Checking Out from Subversion
After checking out from Subversion (SVN) you need to run any of the Ant targets for the workspace to recognize if it is the Community or Enterprise Edition, for example:
bin/ant initThis copies files into the right location and creates the res/edition.properties file to flag that this has been done.
After checking out the project, there will be errors in the IDE as some source files (i.e. Web Services stubs) are not yet generated. The errors will disappear after configuring and building SignServer.