Hi @georhe6 , 1. Looks like your Dispatcher rules are an effective first-level defense. They prevent unauthenticated users from reaching common login endpoints from the publish tier or the internet, which is crucial. Here’s a slightly enhanced version of your rules for clarity: /0300 { /type "deny"...

@bagwanpankaj  Unfortunately, you cannot change or control the purge scheduler programmatically in AEMaaCS. However, if you need more frequent or targeted purging, here are a few options: Custom workflow cleanup service (with caution) You can create a custom OSGi service that: Queries the var/work...

Hi @Anilkumar9, It’s possible the policies haven't been properly deployed or linked. Please try the following steps: Verify if the policies are deployed on your instance via CRXDE Lite at /conf/your-site/settings/wcm/policies/.... Check if your container component's policy exists. Make sure the p...

Hi @TapasaranjanSa3, The search block in AEM Edge Delivery Service (EDS) with Universal Editor is powered by a client-side implementation that queries a pre-built search index. To extend or customize the OOTB search block, you'll typically override the default block behavior and connect it to your o...

Hi @Vishal_Kagde, You don’t need to manually get a ResourceResolver - Groovy Console already runs with one. Try this: def rootPath = "/content/my-site/en/archive" def templatePath = "/conf/myproject/settings/wcm/templates/article" // Update if full path is needed def resources = getPageManager().g...

Hi @bagwanpankaj, In AEMaaCS: The purge services (eg. com.adobe.granite.workflow.purge.Scheduler) are managed internally by Adobe. Adobe removed the cronExpression/scheduler.expression fields from customer configuration to avoid overload and ensure consistent system performance across Cloud enviro...

Hi @newbie34, Instead of trying to deny access to the global button definition, can you deny the permission to delete the page nodes themselves under /content/A. AEM uses JCR permissions to determine what buttons to show - if the user cannot delete the page node, the "Delete" button won't show for t...

Hi @NavyaVo, To add a custom HTTP response header at the Dispatcher level, you'll need to update the Apache HTTPD configuration via the dispatcher.yaml or directly in a custom config under /conf.d. Here's how you can do it: Add Header Using Apache Directive In your custom virtual host config (eg. *....

Hi @stiegjo22, Setting default policies for Experience Fragments (XF) is usually done via a template-level configuration, not directly in the XF itself. You're on the right track by looking into the wcm/core/components/policies/mappings, but to avoid manually assigning policies every time you create...

Hi @Kamaraj_AEM, Please Raise an Adobe Support Ticket  - Since this affects all environments and is directly related to a recent SDK jar update, Adobe support should be made aware. You can attach: The current /libs/granite/dispatcher/content/vanityUrls.html output A list of working vanity URLs bef...