DocumentationExperience Cloud KCS

Enable LTV signing in AEM Forms when migrating signer certificates

Last update: October 16, 2026

This article explains how to enable Long-Term Validation (LTV) signing in Adobe Experience Manager (AEM) Forms when migrating signer certificates and ensure compatibility and compliance during the process.

Description description

Environment

Adobe Experience Manager (AEM) Forms

Issue/Symptoms

When migrating signer certificates in AEM Forms, ensure that LTV signing remains functional and compliant.

Common considerations include:

  • Verifying support for larger key sizes and hash algorithms.
  • Embedding all required revocation information in signed documents.
  • Understanding relevant configuration settings.

Without proper configuration, signed documents may not include all necessary revocation data, which can impact LTV validation.

Resolution resolution

Follow the steps below to resolve the issue:

  1. Verify supported key sizes and hash algorithms.

    • AEM Forms supports 4096-bit key sizes and the SHA384 hash algorithm for signer certificates.

  2. Adjust the Signature Service configuration.

    • In the AEM Forms admin console, navigate to the Signature Service configuration.
    • Locate the Maximum Size Of Revocation Archival Info setting. The default value is 10 KB.
    • Increase this value if needed to ensure all required revocation data is embedded in the signed PDF. If the revocation data exceeds this limit, not all information is embedded, which can affect LTV validation.

  3. Enforce embedding of revocation information.

    • In the Signature Service configuration, review the Enforce Embedding of Revocation Info For All Certificates During Signing/Certification setting.
    • If set to true, signing or certification fails if valid revocation information for all certificates isn’t embedded. The default value is false.
    • Adjust this setting based on your compliance requirements.

  4. Validate in a test environment.

    • Before applying the changes in your production environment, validate the configuration in a test environment to ensure LTV signing works as expected with the new certificates.

  5. Verification

    • After making these changes, sign a document and verify that LTV is enabled and all required revocation information is present in the signed PDF.
recommendation-more-help
experience-cloud-kcs-help-kbarticles