Hi,This configuration makes sure RTE editor content gets filtered to avoid XSS attacks. This feature is pending official addition to the Adobe docs:com.adobe.cq.ui.wcm.commons.internal.servlets.rte.RTEFilterServlet is the new generic servlet introduced that returns the content filtered (through the ...

Hi,You need to use rep:glob type ACLs to do what you want, see here:https://helpx.adobe.com/experience-manager/kb/how-to-leverage-rep-glob-aces-to-manage-permissions-on-multi-ten0.htmlThanks,Andrew

To find the complied JSP files for debugging you can do the following:1. Go to http://host:port/system/console/bundles/org.apache.sling.commons.fsclassloader2. Get the Id bundle3. On the file system go to crx-quickstart/launchpad/felix/bundleX/data/classes where X is the Id value from step 2.4. You ...

I searched our bug tracker and I couldn't find a matching issue.  However, I have seen some cases where somebody tries to terminate a workflow during an AEM restart and it picks up the Sling POST servlet instead of the workflow servlet.  In these cases this node gets corrupted: /var/workflow/instanc...

Hi Kishore,There is no ability to edit the xml file via dialogs.  However, there shouldn't be need to edit the configuration so often.  Antisamy xml format supports regular expressions.  That makes it so you can define complex rules.More details can be found here:https://www.owasp.org/index.php/Cate...

You need to overlay this file [1] under the /apps directory via CRXDE:[1] /libs/cq/xssprotection/config.xmlSee related doc here: Security Instructions:1. Go to http://{aemhost}/crx/de/index.jsp2. Browse to /libs/cq/xssprotection/config.xml and right-click the file then select Copy3. (Skip this step ...

Unfortunately the runmode doesn't get picked up by these automatically.  You have to update the Resource Resolver configuration to point to your custom mapping path.  Per the doc [1]:You can use /etc/map.publish to hold the configurations for the publish environment. These must then be replicated, a...

This looks like it might be related to product issue CQ-4246095 which was a bug related to parsys and the template editor.  A fix was included in AEM 6.3.3,  6.4.4 and 6.5.0.   Please test on one of those versions.

Since the anchor isn't sent to the server you could add javascript to the client library category loaded for the /cf URL.  /cf is handled by this node /libs/wcm/core/content/contentfinder which loads javascript for the "contentfinder" xtype - /libs/cq/ui/widgets/source/widgets/wcm/ContentFinder.js. ...

This may not work as Joerg has mentioned because the anchor doesn't get sent to the server.