AEMFD Signatures bundle remains inactive after AEM Forms installation or upgrade
AEMFD Signatures bundle activation can fail after installing or upgrading AEM Forms, leaving the bundle in a Resolved or Installed state. The issue occurs when required RSA or BouncyCastle cryptographic classes are unavailable to the OSGi framework, or when outdated cryptographic JARs override the correct providers. Common indicators include NoClassDefFoundError and NoSuchMethodException errors in startup and error logs. Adding the required boot delegation configuration or removing obsolete crypto JARs restores bundle activation. Verify the bundle status and dependent services after the update.
Description description
Environment
- AEM Forms
- Adobe Experience Manager as a Cloud Service (AEMaaCS)
- Automated Forms Conversion Service
Issue/Symptoms
- The AEMFD Signatures bundle remains in a Resolved or Installed state.
- Manual bundle startup fails.
- Error logs contain NoClassDefFoundError: com/rsa/jsafe/provider/JsafeJCE.
- Error logs contain NoSuchMethodException: com.rsa.crypto.jcm.ModuleLoader.load(…).
- Cryptographic provider initialization failures appear during startup.
- Signature-related services do not function correctly.
Cause
The AEMFD Signatures bundle requires RSA JsafeJCE and BouncyCastle cryptographic providers to be visible to the OSGi framework. Missing boot delegation entries prevent these classes from loading and cause startup failures. In some environments, outdated cryptographic JARs override the required providers and prevent bundle activation.
Resolution resolution
To resolve this issue, follow these steps:
- Open
error.logand search forNoClassDefFoundError: com/rsa/jsafe/provider/JsafeJCEorNoSuchMethodException: com.rsa.crypto.jcm.ModuleLoader.load. - Confirm that adobe-aemfd-signatures is in the Resolved or Installed state in
/system/console/bundles. - If class-loading errors reference RSA or BouncyCastle providers, add the required boot delegation configuration.
- For cloud deployments, deploy the boot delegation configuration through code and verify that the configuration appears in the OSGi Configuration Manager after deployment.
- Restart the AEM instance and confirm that the bundle becomes Active.
- If errors indicate cryptographic module loading conflicts, remove outdated cryptographic JARs from the extension directory in supported on-premise environments.
- Restart the instance and verify that startup completes without cryptographic initialization errors.
- Verify that dependent services are in a satisfied state and that signature-related operations complete successfully.