Resolving 503 error on /bin/aforbes/pdf endpoint in Adobe Experience Manager when accessed from iPhone devices
This article explains how to resolve a 503 Service Unavailable error that occurs on the /bin/aforbes/pdf endpoint in Adobe Experience Manager (AEM) when accessed from iPhone devices. The solution involves ensuring that the DocAssuranceService bundle is active and removing incompatible cryptographic JAR files.
Description description
Environment
Adobe Experience Manager (AEM) with AEM Forms (all versions).
Symptoms
Requests to the /bin/aforbes/pdf endpoint result in an HTTP 503 Service Unavailable error when made from iPhone devices. The error message may state: “Failure: DocAssuranceService is unavailable. Verify AEM Forms DocAssurance service is installed and active.” The issue is reproducible from iPhone devices. There is no confirmation that Android or other device types are affected.
Cause
The 503 error occurs because the DocAssuranceService bundle is not active due to incompatible or duplicate cryptographic JAR files, which prevent the service from being available.
Resolution resolution
Follow the steps below to resolve the issue.
-
Access the AEM Web Console on all relevant AEM instances.
-
Verify that the AEMFD DocAssuranceService Client Bundle (
adobe-aemfd-docassurance) is in the ‘Active’ state. -
Check the
sling.propertiesfile (located undercrx-quickstart/conf) and confirm that the following property is present:sling.bootdelegation.class.com.rsa.jsafe.provider.JsafeJCE=com.rsa.* -
Stop the affected AEM instances.
-
Navigate to the
launchpad/extdirectory and remove the following JAR files if they are present:cryptojcommon-6.0.0.jarcryptojce-6.0.0.jar -
Restart the AEM instances one at a time.
-
After restarting, ensure that the signature bundle and DocAssuranceService component are active on all instances.
-
Test the
/bin/aforbes/pdfendpoint from an iPhone device to confirm that the 503 error is resolved.