What’s new in this release
- [Bug fix] Sign document error when using Azure Key Vault –
DefaultSignatureLengthparameter (SIGNATURENET‑5654)
This maintenance release focuses on a critical stability issue that affected PDF signing through Azure Key Vault when a custom hash algorithm was used. The internal DefaultSignatureLength value was too small for the generated signature, causing an exception. The limit has been raised, so the same code now signs documents successfully without any changes.
Fixes and enhancements
| Issue ID | Category | Summary |
|---|---|---|
| SIGNATURENET‑5654 | Bug | Increased DefaultSignatureLength to support signatures generated via Azure Key Vault custom‑hash flow. |
Details
- Issue: Signing a PDF with Azure Key Vault and a custom hash failed because the default buffer for the signature was insufficient.
- Resolution: The default buffer size is now large enough to hold the full signature payload, eliminating the runtime error. No API changes are required for existing implementations.
How to get the update
- NuGet – Upgrade to the latest GroupDocs.Signature package via NuGet. Use the version that matches your target framework, e.g.:
dotnet add package GroupDocs.Signature --version 26.2
- Direct Download – Download the compiled assemblies for .NET from the GroupDocs.Signature for .NET 26.2 release page.
Resources
- Full Release Notes – https://releases.groupdocs.com/signature/net/26.2/
- Documentation – https://docs.groupdocs.com/signature/net/
- Support Forum – https://forum.groupdocs.com/c/signature/