Hi @NageshRaja, In addition to @Shiv_Prakash_Patel Verify: In DevTools/HAR, check Cookie: header for login-token= with no value. See if this helps: Logout/SSO: Don’t set a blank cookie - expire it instead:Set-Cookie: login-token=; Path=/; Expires=Thu, 01 Jan 1970 00:00:00 GMT; HttpOnly; Secure Sta...

Hi @Mohanasundaram, Adding a rule named href won’t help - href isn’t a JCR property on your node; it’s an HTML attribute inside the text string. Oak indexes JCR properties, not HTML attributes. So you must either search/index the text property correctly, or store the URL in its own property and inde...

Hi @RahulSi13, Policies don’t auto-inherit into container contexts. The Video/Embed you drop inside a Carousel uses the Carousel’s panel container policy, not the page’s. Here is how you can fix (Template Editor - best practice): Open your page’s editable template - select the Carousel - Edit polic...

Hi @ikno1, That message means your Adobe ID isn’t linked to an Experience Cloud org with AEM entitlement, so Software Distribution hides the downloads. Ask your Adobe admin (or partner/reseller) to add your work Adobe ID to the company org in Adobe Admin Console and assign an AEM product profile. ...

Yes, that’s correct. When you build an Experience Fragment in AEM for use in an external app (like your Ionic/Angular portal), authors will usually only see a basic styled version in the AEM editor. The “lightweight” part means the XF shouldn’t depend on your site’s global clientlibs - instead, the ...

Hi @Jon_Maguire, You don’t need to bring your full AEM site clientlibs into the portal. Experience Fragments (XFs) are meant to be consumed as content, not as a way to load page-level CSS/JS. Best practice is: Author portal-friendly XF variants that don’t rely on your global clientlibs. Keep them l...

Hi @garimak, Here’s the recommended approach for keeping DAM assets secure on Publish in AEM as a Cloud Service. Short version: don’t rely on ACLs alone- enforce authentication at Sling + Dispatcher, and make sure nothing gets cached publicly. What to do (battle-tested setup) Require login for the ...

Hi @tinsel26, Short answer: yes - don’t upload separate “mobile/tablet/desktop” assets. Use the Core Image component’s responsive widths (srcset/sizes) and, if you need different crops per breakpoint, layer in Dynamic Media Smart Crop. That gives authors a single image to pick while AEM delivers the...

Hi @Randeep_virk, In Local SDK, the ImageRef._dynamicUrl field is not populated (it’s provided by Asset Delivery, which only works in the cloud env after it’s configured). When you query: image { ... on ImageRef { _dynamicUrl } } the resolver can’t produce a Dynamic Media/Asset-Delivery URL locall...

Hi @ViaVu, Please refer this if it helps: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/how-to-change-aemaacs-environment-indicator/m-p/645515 https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-environment-indicator-in-aemaacs/m-p/564028