The ADSS Client SDK is full of features that help streamline integration, including:
- API documentation, release notes and upgrade instructions
- Libraries and source code samples for Java and C#
- Go>Sign client and deployment documentation
- Example web application with source code for Go>Sign client
- WSDL and Schema files to help developers interact with ADSS Server in other programming languages, such as PHP and C++
ADSS Client SDK is designed to work with your business, and supports the following signature formats:
- PDF
- XML
- DSig
- PKCS#7
- CMS
- S/MIME
- ETSI AdES –T, -C, -X, -X-Long and –A formats
- PDF
- PDF
Additionally, it supports local hashing of data and signature handling and embedding for PDF documents.
ADSS Client SDK meets the following standards and compliance requirements:
- Signature generation and verification:
- CMS/PKCS#7
- PDF signatures
- XML DigSig
- ETSI PAdES, CAdES, XAdES (ES, -T, -C, -X, -X-Long, -EPES and –A
- S/MIME
- Signature and verification protocol:
- OASIS DSS and DSS-X v1.0 over SOAP/XML
- HTTP/S
- Certificate validation:
- Certificate Revocation Lists (CRLs) – including delta and indirect CRLs
- OCSP
- SCVP
- XKMS
- OASIS DSS-X
- Certificate generation:
- PKCS#10
- PKCS#12
- PKCS#7
- X.509v3 (Certificate Authority service supports CMC protocols)
- Quality ratings:
- PEPPOL quality ratings for DSS-X and XKMS protocols
- HSM Support:
- Any PKCS#11 compliant HSM, smartcard or token
- SafeNet, nCipher and others
- Languages:
- Java 6
- Java 5 (on request)
- .NET on Windows 32/64 servers
Users can sign any document or file directly within their Windows-based desktop applications. In addition, the file format is retained after the signing process. This ensures you don’t need to worry about converting to PDF or other formats. Virtual CSP works with the following applications, including:
- Microsoft Word
- Microsoft Excel
- Microsoft Outlook
- Adobe Acrobat Professional
- Custom desktop applications
Contact our team to discuss your individual requirements.
Access to your signing keys is protected through Ascertia’s Secure Activation Protocol (SAP). It ensures strong user authentication and authorisation. It is a two factor-based approach using Ascertia’s Go>Sign app.
Ascertia’s Virtual CSP user interface (UI) is multilingual and supports the following languages:
- English
- Arabic
- French
- Portuguese
- Additional languages are available on request
Ascertia’s Virtual CSP can be white-labelled. Contact our team for further details.
Ascertia’s Go>Sign application is designed for digital trust. We ensure High Trust Security by:
- Generating authorisation keys using Elliptic Curve algorithm
- Storing keys in the mobile device’s secure enclave
- Using Touch ID or Device PIN to access the secure enclave
- Embedding signing evidence inside the digitally signed authorisation response
- Using AES 256-bit encryption over TLS/SSL
Using Go>Sign helps assist in achieveing EU eIDAS Qualified Remote Signing (TS 419 241 level 2 Sole Control) for server-side signing