SigningHub now supports the Cloud Signature Consortium (CSC) v1.0.4.0 API protocol, this enables customers to leverage Remote Signing Service Providers (RSSP) for signing documents. Support for CSC within SigningHub now means customers can not only 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.
SigningHub now allows ADSS Server generated signing certificates to be imported for a user by a system admin. A system admin can import multiple certificates for a user using a friendly capacity name.
Where a certificate used for document signing has a LEI (Legal Entity Identifier) 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 Global Legal Entity Identifier Foundation (GLEIF).
Microsoft Azure Active Directory and Office 365 support has been added at the point of signing on the 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 CSC protocol for signing.
In previous releases signing profiles were configured under service plans, as of SigningHub 7.7.9 these 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.
As of SigningHub 7.7.9, the term “Witness signing” has been deprecated. 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 Ascertia Customer Support for assistance.
Signature types (electronic or digital signatures) are now based on the level of assurance which is set by the document owner, a document owner can add a signature field and assign the required level of assurance. Level of assurances includes eSeal, Advanced Electronic Signature, Qualified Electronic Signature and High Trust Advanced (AATL).
Server side and client-side signing has been moved from the service plan configuration to the signing server’s configuration.
Remote authorisation configurations have been removed from the service plan and added to the signing profiles along with other configurations of Office and XML signing profiles.
Signing methods for web browsers and mobile apps are now controlled through the same configuration settings under the enterprise roles.
A “Readme” notice has been built into the installer wizard to allow additional information to be added on each SigningHub release.
