SigningHub v10.0.2

August 2025

New Features

Microsoft Entra ID/Azure Active Directory auto provisioning (SHE-24850, SHE-40215)

SigningHub now supports SCIM-based (RFC7642) auto-provisioning for Microsoft Entra ID (formerly Azure Active Directory). This enables automatic provisioning and synchronisation of Entra ID/Azure AD users in SigningHub.

Trusted Device Authentication (SHE-49625, SHE-53628)

SigningHub now supports Trusted Device Authentication to enhance login security. When enabled, users must complete OTP verification on unrecognised devices based on configured secondary authentication options. Upon successful verification, the device is marked as trusted, and a notification email is sent with device and location details.

---

Improvements

Improved 2FA Setup Experience (SHE-49533)

SigningHub now presents a setup dialogue for two-factor authentication, enabling users to configure it immediately—removing the previous dependency on email.

Trust1Connector TrustStore Support for Local Signing (SHE-49598)

SigningHub now supports Trust1Connector TrustStore for signing documents using locally stored certificates from keystores on Windows and macOS. This enhancement requires the Trust1Connector JS SDK version 3.8.5 or later.

‘Get Smart Form URL (Integration)’ API (SHE-51789)

The ‘Get Smart Form URL (Integration)’ API is now available to generate secure SmartForm embed links for use within iframes. To enhance security, only whitelisted domains configured in the integration settings are allowed to display SmartForms.

Previous Password Retention Count (SHE-36237)

SigningHub now allows administrators to specify the “Previous Password Retention Count,” which restricts users from reusing any retained passwords.

Service Plan Upgrade Notifications (SHE-52715)

Administrators can now configure when enterprise owners should be notified if a service plan is marked as deprecated. They can define the number of days before expiry to display a dashboard banner and set how many email reminders are sent to users.

Visual Guidance for Assigned Fields (SHE-52984)

A visual cue labelled "Start" now appears on the left side of the document viewer when a pending document is opened, guiding users directly to their assigned fields for a more intuitive experience.

Option to Disable HTTPS Redirection (SHE-52882)

SigningHub now allows administrators to disable enforced HTTPS redirection by updating the appsettings.Production.json file. This enhancement enables deployments over HTTP where HTTPS is not required, offering greater flexibility for environments where TLS needs to be terminated at a load balancer.

About API Response Format (SHE-55411)

SigningHub now returns the About API response in JSON format instead of XML, aligning it with the structure of other API responses. Additionally, the default “SigningHub” identifier has been removed to support cleaner and more brand-neutral integrations.

Integrations Enhancement (SHE-49241)

SigningHub now ensures that workflows shared via API and completed on the web, whether directly or through iFrame—publish all related outputs to the configured webhook URL.

ADSS Server XML Response Parsing Enhancement (SHE-45926)

SigningHub is enhancing its XML response parsing to address issues caused by the updated XML namespaces in ADSS Server v8.3.4. The improved implementation will parse XML responses without considering namespaces, ensuring compatibility and accurate processing.

Enhanced Post-Processing Configuration for Completed Documents (SHE-38964)

SigningHub now allows administrators to set an enterprise-level default value for post-processing, so that completed documents are sent to all recipients.

Option to Disable Basic Deep Linking (SHE-54049)

SigningHub now provides a DisableBasicDeepLinking parameter, configurable via the web.config file. When enabled, this prevents browsers from attempting to open the mobile app if it’s not installed, avoiding error messages and ensuring a smoother mobile web experience.

Document Signing and Access Authentication for Unregistered Users (SHE-52980)

In addition to the existing option to enforce document access and signing authentication for all users, SigningHub now allows enterprise administrators to apply this enforcement specifically to unregistered users.

Support for Basic Authentication and Token Introspection in OAuth Connector (SHE-52789)

The OAuth connector now supports Basic Authentication for securely transmitting client credentials and enables Token Introspection through POST requests to validate access tokens and retrieve user information.

Disabled Field Colour Customisation (SHE-50685)

SigningHub now provides an option to customise the colour of disabled fields in documents by configuring Branding Level 9 settings.

Email Notifications for Delegate Signers (SHE-50036)

SigningHub now automatically notifies users via email when they are appointed as a delegate to sign on a user’s behalf or when the delegation period is updated.

Restrict Editing of Company Name and Job Title (SHE-41441)

SigningHub now allows enterprise administrators to restrict users from editing their company name and job title through role-based settings.

Improved Dutch Translations (SHE-55514)

SigningHub now includes updated Dutch (nl-NL) translations to enhance clarity and accuracy across the application.

Certificate Filter Field Values in API Documentation (SHE-55269)

The Add/Update Certificate Filter API documentation has been updated to reflect accurate field values required for successful requests.

Proxy Support for API Communication (SHE-55259)

SigningHub now supports proxy configuration for API communication via the appsettings.Production.json file. This allows deployments to route traffic through a proxy when required, with options to bypass local addresses.

Improved Session Handling for Microsoft Entra ID/Azure AD SSO (SHE-55204)

SigningHub now handles session persistence more reliably when using Microsoft Entra ID/Azure AD Single Sign-On, ensuring consistent behaviour across browsers and tabs.

Improved Handling for Concurrent User Contact Creation (SHE-54916)

SigningHub reliably handles scenarios where the same user is added as a recipient in parallel workflow requests.

Fill Form Fields API (SHE-53281)

SigningHub now fully supports unregistered signers in the 'Fill Form Fields API' using both old scope and new scope tokens.

Improved Login Branding (SHE-52884)

SigningHub now consistently displays correct branding elements, including authentication profile logos, on enterprise URLs during login.

Optimised Notifications for Shared Space Workflows (SHE-52780)

SigningHub now processes user notifications more efficiently in shared spaces, improving/finish button performance for workflows with large user groups.

Corrected Dutch Translation for Invalid PIN Message (SHE-52452)

SigningHub now shows a clearer and grammatically accurate Dutch translation for the LOCAL_SIGN_T1C_MIDDLE_WARE_INVALID_PIN error message.

Support for Danish MitID (SHE-54815)

SigningHub now supports authentication and digital signing using Danish MitID, enabling users in Denmark to securely access and sign documents through their national eID.

Webhook and Workflow Completion Report Documentation (SHE-53921)

SigningHub documentation has been updated to reflect the correct system behaviour for triggering webhooks and workflow completion reports.

Get Contacts API Documentation (SHE-53747)

The SigningHub API documentation has been updated to clarify that the user_national_ID field is only returned when the x-search-text header includes a National ID value (in Base64 format), and the "Allow Users To Add National ID" setting is enabled in the admin portal.

---

New Operating System Support

Windows 2025 Server Support

SigningHub now supports Windows Server 2025 Standard.

---

New ADSS Server Support

ADSS Server Support

SigningHub now supports ADSS Server 8.3.12.

---

Important System Changes

• User inputs containing the following characters will now be rejected: ", ;, --, /*, */, %, <, >, 0x09, 0x0A, 0x0D. Previously saved names with these characters will trigger an error on update.

• The /v4/about API now returns responses in JSON format instead of XML. Integrations relying on the previous XML structure must update their implementations accordingly. Additionally, the default “SigningHub” identifier has been removed from the response.

• The "Require Email Validation" setting is now mandatory and permanently enabled for all SmartForms. Users can no longer disable this option, ensuring enhanced signer verification before accessing and signing the SmartForm.

---

Compatibility with Earlier Versions of SigningHub

SigningHub (iOS) & (Android) 10.0.2 are compatible with SigningHub 10.0.1 except for the changes mentioned in the Important System Changes section.

---

For further details, contact us at [e-mail] or visit www.ascertia.com.

---