On the 28th October Ascertia announced the launch of the SigningHub v7.7.9 release. This release includes support for the Cloud Signature Consortium API protocol and greater control of the sign-off level of assurance for users.
SigningHub v7.7.9 release developments:
As a member of the Cloud Signature Consortium, Ascertia works with a number of Trust Service Providers (TSPs) who are part of this scheme. This partnership ensures essential components of a remote signature solution can be available to consumers.
The latest SigningHub updates ensure high-trust, compliant electronic and digital signatures and interoperability to enable the widespread adoption of remote signing.
SigningHub v7.7.9 release key updates include:
- SigningHub now supports the Cloud Signature Consortium (CSC) v1.0.4.0 API protocol. It enables customers to leverage Remote Signing Service Providers (RSSP) for signing documents.
Support for CSC within SigningHub not only ensures customers can use SigningHub with Ascertia ADSS Signing Server but also independently with a CSC compliant RSSP. - Document owners have greater control over the level of assurance expected from document signers. A document owner can now set the level of assurance required on a signature field.
This configuration enforces document signers to sign the document using the certificate that has the right level of assurance as per eIDAS compliance. Recipients at their end can perform signatures using available signing methods, subject to service plan and allowed options under enterprise role. - Signature types (electronic or digital signatures) are now based on the level of assurance which is set by the document owner – the document owner can add a signature field and assign the required level of assurance.
Level of assurances include eSeal, Advanced Electronic Signature, Qualified Electronic Signature and High Trust Advanced (AATL). - ADSS Server generated signing certificates can be imported for a user by a system admin. A system admin can import multiple certificates for a user using a friendly capacity name. This will enable a user to select the correct certificate at the point signing.
- Where a certificate used for document signing has a Legal Entity Identifier (LEI) set as an extension, the LEI information now appears in the signature verification dialog in SigningHub. The LEI information in the verification dialog also provides a link to the LEI information at the Global Legal Entity Identifier Foundation (GLEIF).
- Microsoft Azure Active Directory and Office 365 support has been added at the point of signing on SigningHub’s mobile web and native apps (Android and iOS)
- Administrators can configure more than one RSSP in the service plan. These signing servers can be different servers supporting the CSC protocol for signing.
- Signing profiles are now configured as RSSPs under service plans using signing profiles. Signing capacities come from certification profiles and can be selected and categorised on the basis of level of assurances.
- All signing profiles that were previously configured for witness signing under service plans have now moved to certification profiles, with a postfix (i.e. _ESEAL), and now have an assurance level of eSeal.
Customers upgrading from previous releases of SigningHub are encouraged to consult the steps in the SigningHub upgrade guide or to contact us for assistance.
