Documentation

AEM integration with Workfront returns error due to missing proxy configuration suffix

Last update: Thu Oct 16 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

Due to a missing suffix in the OSGi configuration, Adobe Experience Manager (AEM) integration with Workfront using the Enhanced Connector for the first time fails with an error. To fix this, create a proxy configuration with the correct suffix and apply it to enable successful API communication between AEM and Workfront.

Description description

Environment

  • Product: Adobe Experience Manager (AEM) and Workfront Enhanced Connector
  • Connector Version: 1.9.21
  • Instance: AEM as a Cloud Service (AEMaaCS)

Issue/Symptoms

  • Error logs show proxy detection issues during Workfront API calls — Workfront API call failed, verify your proxy settings.
  • Initial cloud configuration for the Enhanced Connector can’t be instantiated.

Resolution resolution

Note: This solution applies specifically to AEMaaCS environments where a corporate proxy is used for outbound connections from AEM to Workfront. Before proceeding with these steps, make sure all other configurations, such as API keys and domain names, are correctly set up.

In AEM as a Cloud Service, it is not possible to access the Felix Web Console (/system/console/configMgr) to apply OSGi configurations. All OSGi configurations—including Workfront proxy settings—must be created as configuration files in your project’s codebase and deployed using Cloud Manager.

To resolve the proxy configuration issue for the Workfront connector:

  1. Determine the OSGi Persistent Identity (PID) for the proxy configuration (for example, org.apache.http.proxyconfigurator).

  2. In your project’s configuration folder (ui.config), create a file such as:

    code language-none 
    /apps/<your-project>/config.<runmode>/org.apache.http.proxyconfigurator workfront.cfg.json

Set parameters for your proxy, such as host, port, credentials, etc.

For correct naming and environment targeting, see the documentation:
- Configuring OSGi for Adobe Experience Manager as a Cloud Service
- How to use OSGi configurations in AEM as a Cloud Service?
3. Add the new configuration file to your Git repository and trigger a deployment through Cloud Manager. The configuration will be picked up by the AEM as a Cloud Service runtime.
4. Once deployed, use the Developer Console (via Cloud Manager) to view active OSGi configurations.

recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f