Hi @ManjulaKumar If reverting to the previous (working) certificate still results in the "Deployed" status and not "Verified", it could indicate that the verification process is stuck or the system hasn’t refreshed properly.

Hi @ManjulaKumar 1. Since the cert is already updated in Cloudflare, is it not required to update the cert in Cloud Manager?This is because Cloud Manager acts as the origin server and Cloudflare (when using Full or Full (Strict) SSL mode) still requires a valid SSL certificate at the origin for the ...

Hi @Sb2512 ReferSolved: List of users, groups and permissions - Adobe Experience League Community - 182886Managing Users | Adobe Experience Managerhttp://jackrabbit.apache.org/api/2.18/org/apache/jackrabbit/api/security/user/UserManager.html Use the UserManager API from org.apache.jackrabbit.api.sec...

Hi @ShwetaDe Confirm the process step uses the right implementation class if it’s custom, or the correct OOTB delete process. You can add a log step or debugging to confirm the payload paths before the delete step. Check if the workflow uses a service user mapping (system-user-mapping) and confirm t...

Hi @anasustic you can try this way <metadata sling:hideResource="{Boolean}true" jcr:primaryType="nt:unstructured" jcr:title="Metadata" sling:resourceType="granite/ui/co...

Hi @Rudra-2024 This behavior you're encountering with AEM's Multi Site Manager (MSM) is indeed expected and can be explained by how MSM handles page rollouts and node creation. Why This Behavior Occurs When you move a page within the Language Master and then rollout the changes to the live copy, AEM...

Hi @RickTr  when moving a page to a new URL within the same site in AEM the best approach is to use a 301 redirect.Add a 301 redirect in the dispatcher configuration or Apache web server (or CDN level like Akamai) pointing from the old path to the new one. /old-page-path.html /new-page-path.html R=...

Hi @S__k__Agarwal  AEM Mocks provides developers access to the following services: TagManager (Option C)ModelFactory (Option E)

Hi @S__k__Agarwal you can follow below approach Make the allowed Parents property of template T match the template of page P.

Hi @S__k__Agarwal  These two properties are essential for ensuring that your custom index is applied correctly to queries on the /content/mywebsite path. So, my recommendation is: The custom OAK lucene index is missing evaluatePathRestrictions property and includedPaths property