I was trying to setup a replica of dispatcher on a Linux environment same as how we have on AEM as Cloud.  I was able to extract the files using the below command:./aem-sdk-dispatcher-tools-<version>-unix.sh Can someone tell me what are the next steps to configure the dispatcher on Linux? When I ran...

Hello Everyone, Hope everyone is doing good! I was trying to modify the OOTB request for activation workflow and while building the code for AEM as Cloud Service I am getting the below error. +- <MAJOR> /conf/global/settings/workflow/models/request_for_activation/jcr:content [restricted resource typ...

Hi @selvendranr9588 Could you please provide some more informaiton regarding the use case that you want to achieve using these headers from clientside?

Hi @ckonfrst  Did you check the same issue on any other browser on Mac Monterey? Ideally it should not break, but if it is then you need to wait until a fix for this is provided by Google Chrome. Thanks!

Hi @selvendranr9588  By default AEM managed CDN adds headers to each request with x-aem-client-country and x-aem-client-continent header. If your publish instance is managed via AEM Cloud Manager then it should appear. If not raise a ticket with Adobe Support and they should be able to resolve the i...

Hi @raviranjan  Out of the box, AEM denies all server names or hosts to make HTTP request to the respective running AEM publish/author instance. During a HTTP request made to the AEM publish/author, AEM checks the Referrer header configuration. If the referrer configured to allow the host(s), then A...

Hi @Hugh_Shao  No. Siteadmin will not be accessible on AEM as Cloud and the same can be achieved using the AEM Sites (/sites.html/content). Access Rights can be managed here: /security/permissions.html/principal/everyone Thanks!

Hi @kevingtan  Please stop the instance. Update the start script with the below line: if [ -z "$CQ_RUNMODE" ]; thenCQ_RUNMODE='publish,dev,crx3,crx3tar,nosamplecontent'fi Start the instance and it should fix the issue. Thanks!

@Ronnie09 Do you mean AEM 6.5? In that case you need to upgrade the core component version manually and it will be fixed. Update the below 2 dependency on your project pom or manually download and upload the core module on AEM. <dependency> <groupId>com.adobe.cq</groupId> <artifactId>core.wcm....

Please upgrade AEM version from 6.5.0 to 6.5.10.0 by installing the latest service pack. Also upgrade the uber jar version from 6.5.0 to 6.10.0 Thanks!