GroupDocs.Signature for Python via .NET 25.4 Release Notes

GroupDocs.Signature for Python 25.4 Release Notes

GroupDocs.Signature for Python 25.4 introduces important enhancements to digital signature functionality and document handling, along with critical bug fixes that improve the overall user experience.

What’s New in This Release

KeyCategorySummary
SIGNATURENET-5392✨ EnhancementEnhanced digital signature functionality with LTV (Long-Term Validation) support
SIGNATURENET-5367✨ EnhancementImproved document loading with file type specification (Stream or File)
SIGNATURENET-5163🔧 FixFixed duplicate PIN prompts during smart card authentication for PDF signing
SIGNATURENET-5291🔧 FixResolved issue with barcode signatures persisting after removal operations
SIGNATURENET-5450✨ EnhancementCreated documentation for GroupDocs.Signature for Python via .NET
SIGNATURENET-5452✨ EnhancementImplemented generation of the documentation references and autocomplete file for Python deployment

Enhancements

Implemented generation of the documentation references and autocomplete file for Python deployment

We’ve created comprehensive API reference documentation with intelligent code completion support to accelerate your development workflow. The new reference includes detailed information about all classes, methods, and parameters, along with autocomplete files that provide real-time coding assistance in your IDE.

Explore the API reference: https://reference.groupdocs.com/signature/python-net/

Created documentation for GroupDocs.Signature for Python via .NET

Our new user documentation provides everything you need to get started with GroupDocs.Signature for Python. It includes quick start guides, tutorials, comprehensive feature demonstrations, and practical code examples that show you how to implement electronic signatures in your applications.

Visit our documentation portal: https://docs.groupdocs.com/signature/python-net/

Enhanced digital signature functionality with LTV (Long-Term Validation) support

We’ve significantly improved our digital signature capabilities by adding Long-Term Validation (LTV) support for PDF documents. This critical enhancement ensures that digital signatures remain verifiable and valid even after the signing certificate expires.

Key Benefits:

  • Guarantees long-term signature validity and verification
  • Embeds all necessary validation data within the document
  • Complies with advanced electronic signature standards
  • Ensures document integrity for archival and compliance purposes

Implementation: Simply enable LTV support through the new useltv property in the DigitalSignOptions class:

with gs.Signature(sample_pdf) as signature:
    options = gso.DigitalSignOptions(certificate_pfx)
    options.image_file_path = image_handwrite
    options.left = 50
    options.top = 50
    options.page_number = 1
    options.password = "1234567890"
    # Enable Long-Term Validation
    options.useltv = True
    
    result = signature.sign(output_file_path, options)
    print(f"\nSource document signed successfully with {len(result.succeeded)} signature(s).")
    print(f"File saved at {output_file_path}.")

Improved document loading with file type specification (Stream or File)

This enhancement gives developers greater flexibility when loading documents by allowing explicit specification of the file type. You can now indicate whether you’re working with a Stream or a File, which optimizes resource usage and improves error handling.

Bug Fixes

Fixed duplicate PIN prompts during smart card authentication for PDF signing

Issue: When signing PDF documents with a smart card, users experienced an inconvenient double PIN prompt due to redundant authentication requests.

Resolution: We’ve implemented an intelligent validation mechanism that detects and prevents multiple PIN prompts during the signing process. This improvement:

  • Creates a smoother authentication experience
  • Eliminates unnecessary user interactions
  • Is automatically applied when using custom hash signing functions
  • Requires no additional configuration or code changes

Resolved issue with barcode signatures persisting after removal operations

Issue: Barcode signatures were not being completely removed from documents when using signature removal operations.

Resolution: We’ve corrected the underlying issue in our signature removal mechanism to ensure that barcode signatures are completely and properly removed from documents. This fix ensures data integrity and prevents potential security or privacy concerns from lingering signature data.

Upgrade Instructions

To leverage these improvements, update your package reference to version 25.4:

pip install --upgrade groupdocs-signature-net