Dear GroupDocs customers,
We are pleased to announce the release of GroupDocs.Signature for .NET v26.2. This update resolves a critical issue reported by a customer using Azure Key Vault for digital PDF signing and improves overall signature processing reliability.
Background
A customer reported an issue where signing PDF documents using a custom hash via Azure Key Vault failed with a DefaultSignatureLength error. The internal signature buffer was insufficient for high-security signatures generated through Azure Key Vault’s HSM-backed signing flow. We investigated, implemented a fix, and the customer has confirmed that the issue is now fully resolved in v26.2.
Key Fixes & Improvements
- Azure Key Vault Signing Fix (SIGNATURENET-5654): Resolved the
DefaultSignatureLengtherror that caused PDF signing failures when using Azure Key Vault’s custom hash signing flow. - Optimized Buffer Handling: Internal signature length parameters have been adjusted to fully support high-security cloud-generated signatures.
- Zero Code Changes Required: Simply update the NuGet package — no changes to your existing implementation are needed.
Useful Links
- Original Customer Discussion – Full context of the reported issue and resolution
- Full Release Notes – Technical details of the SIGNATURENET-5654 resolution
- Download from NuGet – Update your project to v26.2
- How to Sign Documents in .NET with PKCS#11 USB Dongles, Smart Cards & HSMs
- Custom Hash Sign with Azure Key Vault
If you use Azure Key Vault for document signing, we recommend upgrading to this version for improved reliability.
We’d love to hear your feedback! Let us know if you have any questions or feature requests for upcoming releases.
Best regards, The GroupDocs Team