Document Trust Manager

Fixed an issue where, when an invalid PIN is sent to the /credentials/authorize endpoint in the CSC API, the API now returns a 400 Bad Request status with the message “The PIN is invalid” instead of a 500 Internal Server Error.

The signing widget on the dashboard now displays the total number of hashes successfully signed, rather than the total number of successful signing requests.

Fixed an issue where CertCentral order placement audit logs were not displayed correctly.

Added support for sorting of columns on the Document Listing page.

Fixed filtering on the Resource ID column on the Credential Listing page.

Fixed an issue in which reports failed to complete and remained in a processing state when the start date was configured to be after the end date.

When the configuration flag feature.certcentral.end2end.flow.for.create.credential.by.signer.enabled is enabled, the Create credential flow for client admins now completes without redirecting to the consent URL. Instead, the credential is created directly within the end-to-end flow.

Fixed an issue that caused organization and authorized representative information to not appear correctly on the CertCentral Integrations page.

Resolved a problem where duplicate orders could occasionally occur during onboarding through the SEP link.

Users who had a previous order rejected or canceled in CertCentral can now easily restart onboarding through the SEP link using the same username.

Improved error handling by fixing API response statuses where DTM was returning a 500 Internal Server Error instead of a 400 Bad Request.

Released a new version (1.1.3) that includes a fix for an issue where timestamp, OCSP, CRL requests were bypassing the proxy in cases when proxy server was enabled.

With this fix, only one authorized representative is required to order Natural Person with Organization and eSeal products in Switzerland.

Added a new feature where approval by Client administrator is required when Singers are onboarded using a product based signup link. Approval is required only if auto-approval is not set while creating the signup link or signer email domain does not match.

Updated UI and emails translations.

Added the ability to filter by username on all listing pages.

Released new version (1.0.3) of Content Signing Service, featuring:

Added the ability to download remote identity verification evidence for partner customers.

Fixed validation approval for deleted users in Account Manager.

Fixed the error received when calling Enhanced Signature API with CertCentral issued AATL certificates.

Made significant style updates to the platform to improve the user experience in the Document Trust section of DigiCert ONE. We will continue making additional design and styles changes in future releases.

Fixed pagination issues in CSC credentials/list API.

Added new API with the ability to download remote identity verification evidence for CertCentral issued credentials.

This release contains various backend updates to improve the overall user experience.

Released new version of Content Signing Service (1.0.2) featuring:

Enhanced validation of the phone number field in “Add authorized representative” form on signup link creation and CertCentral integration pages.

This release contains various backend updates to improve the overall user experience.

Released new version of true-Sign V Client for Windows (4.1.3) and macOS (1.0.6). The new versions introduce updated ICA and root for CH and NL signing certificates issued through CertCentral.

This release contains various backend updates to improve the overall user experience.

This release contains various backend updates to improve the overall user experience.

This release contains various backend updates to improve the overall user experience.

Added the ability to filter by creator on the audit log details page.

Fixed an issue where a warning appeared in Swiss signature validator if validating signed PDFs by adding timestamp certificate chain and Online Certificate Status Protocols (OCSPs) to the Document Security Store (DSS) of the PDF document.

Fixes to the DSS of the PDF document are done if:

Updated swagger documentation with the correct status code in:

POST api/v1/document
POST api/v1/document/{documentId}

This release contains various backend updates to improve the overall user experience.

This release contains various backend updates to improve the overall user experience.

Released new version of SealSign 2.0 Client (1.1.1) featuring:

Added the ability to filter reports by date and time on the Audit logs page.

Added OpenAPI JSON and YAML support.

Fixed an issue where some users were unable to revoke their credentials.

Fixed content errors in “Sign with your digital ID” email notification.

PDF Service 2.0 changed to Content Signing Service with support for XML signing (XADES).

Fixed timestamp signature to show correct hash value in the signature sent in CSC timestamp API.

Added contextual help for creating signup links to guide administrators.

Released new version of SealSign 2.0 Client (1.1.0) featuring:

Released new version of true-Sign V Client for macOS (1.0.4). The new version introduces new enhancements:

Fixed error in the credential expiry email.

Access token generated from client credential flow can be used in the APIs below:

POST /documentmanager/api/v1/credential/authorize 
POST /documentmanager/api/v1/credential/authorize/<pending_id>/resend-email 
GET /documentmanager/api/v1/credential/authorize/<pending_id> 
POST /documentmanager/api/v1/credential/extendTransaction

Added product name on signup link details page.

Added CSC v0 and v1 endpoint details.

Removed old API endpoint for recreating credential by validation.

Added the ability to filter by name column on the Credential listings page.

Users will be notified via email before credential expiry.

Added the ability to filter by username on the Credential listings page.