ÃÛ¶¹ÊÓƵ

Documentation

Content fragment edit fails due to redirection in AEMaaCS

Last update: Tue Jul 08 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

In ÃÛ¶¹ÊÓƵ Experience Manager as a Cloud Service (AEMaaCS) – Assets, you are redirected away from the intended editing interface when trying to edit a content fragment through the new Content Fragment (CF) UI. To resolve the issue, create or update theÌýfile org.apache.sling.security.impl.ReferrerFilter.cfg.json to allow valid hosts.

Description description

Environment

  • Product: ÃÛ¶¹ÊÓƵ Experience Manager as a Cloud Service (AEMaaCS) – Assets
  • Instance: Development

Issue/Symptoms

  • Editing content fragments redirects users to an unintended interface.
  • Redirection occurs only when using the new Content Fragment UI.
  • Direct access to edit URLs works without issue.

Resolution resolution

To resolve the issue, follow these steps:

  1. Deploy the following updated OSGi configuration in the ui.config module:

    code language-none 
    {    Ìý "allow.hosts.regexp": [     Ìý Ìý "https://.*\\.adobe\\.com:443",    Ìý Ìý "https://.*\\.adobe\\.net:443",    Ìý Ìý "https://.*\\.workfront\\.com:443",    Ìý Ìý "https://.*\\.workfront-dev\\.com:443",    Ìý Ìý "https://.*\\.dev\\.workfront\\.tech:443"    Ìý ] ,    Ìý "filter.methods": [     Ìý Ìý "POST",    Ìý Ìý "PUT",    Ìý Ìý "DELETE"    Ìý ]     }

    Ìý

  2. Create or update the file org.apache.sling.security.impl.ReferrerFilter.cfg.jsonwith:

    • Define allowed hosts using regular expressions for your domain.
    • Specify the HTTP methods POST, PUT, and DELETE to be filtered.

  3. Deploy the updated OSGi configuration to your environment.

  4. Verify that content fragments open in the correct interface without redirection.

Note: After confirming the fix, consult your product team before enabling this configuration in production.

Content Fragments in the AEMaaCS user guide.

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