Adobe Experience Manager Sites

There appears to be a short window during system startup where the OSGi Management Console (/system/console) can be accessed using default or static credentials (e.g., admin:admin).This window can allow unauthorized users with network access to gain admin rights if they know or guess the password, before the usual authentication/authorization mechanisms and custom user configs are fully in place.What are best practices to completely prevent unauthorized access to /system/console during (and after) startup?

Hi Community,I am experiencing an issue where a page in the AEM Author environment displays a grey/blank screen when opened in Edit mode. The page is accessible on the published environment and appears to function as expected there.We are trying to understand the possible causes and recommended troubleshooting approaches for this type of behavior.A few questions:What are the common reasons an AEM page might display a grey/blank screen in Author while working correctly on Publish? Are there specific logs, tools, or debugging techniques you typically use to identify the root cause? Have you encountered situations where page components or page content caused Author rendering issues? What is the best approach to isolate the problematic component or configuration when the page itself cannot be opened normally in the editor?Any suggestions, best practices, or experiences would be greatly appreciated. Thank you.

 I’ve been facing an issue in RTE where the links with .aspx extensions were flagged as invalid by linkchecker. Hence I added a override pattern in com.day.cq.rewriter.linkchecker.impl.LinkCheckerImpl.cfg.json with the below pattern:"service.check_override_patterns": [  "^system/",  "^.*\\.aspx(?:$|[?#].*)"]Note: “^system/” was added as default.Even after this change, the .aspx links are still getting flagged as invalid in the linkchecker even though they are valid web pages. How can I fix this?

🙌 Congratulations to ​@gkalyan, AEM Champion of the Month - June 2026! 👏 🏅 Kalyan has gone above-and-beyond in the last year as an AEM Champion, stepping into multiple leadership roles in the AEM User Group Program, internal Adobe product feedback sessions, and Community advisory. He regularly raises his hand to help mentor new and existing customers and serve as an advocate of the Adobe CX Enterprise ecosystem, including as a speaker at internal and external Adobe events like Adobe Summit. Please join us in congratulating Kalyan for this impressive achievement!

Hello team! We are looking for people that have experience with AEM and lives in México, we at Capgemini have some opportunities for you :) 

Large Language Models (LLMs) crawl and ingest origin-level URLs like /content/yoursite even when those URLs are rewritten or hidden from human users. Especially this is happening for home page URLs. How can we identify from where this is happening and how can we minimize this?

Hi Team, Could you please provide your guidance on the following?We recently created an llms.txt file under DAM with some content in it. This file is accessible via the domain (for example: https://www.mycompany.com/llms.txt). URL shortening is being handled through the dispatcher, and the file loads successfully in the browser without any issues. However, when we try to access the same URL through Gemini or any gpt and request it to read the content, it returns an error stating that the file is not accessible or not available on the domain. Since we have Microsoft CDN and AMS WAF rules in place, could you please advise whether we need to validate this at the CDN layer, AMS App Gateway WAF rules, or the dispatcher level? Thanks in AdvanceRegradsVeera 

👉 Calling all AEM practitioners in the San Francisco Bay Area and beyond ‼️👋We're thrilled to announce the launch of the AEM User Group - Bay Area chapter! Hosted by seasoned AEM experts KrishnaKalyan Gorthi and Mrinal Kumar, this is a community dedicated to passionate AEM users who come together to share best practices, collectively problem solve, and network.This chapter will host in-person and virtual meetings, so there is no shortage of ways to connect with your peers. 🙌Sign up here: https://aem-augs.adobe.com/aemug-bay-area/

Hi Team,Could you please suggest the best approach for this scenario?I have a component that reads the latest articles from article pages and displays them on a page. Currently, there are around 1500–2000 articles, and the number keeps increasing daily. Because all article links and HTML are rendered directly in the DOM, the page load time has become very high.The current implementation is SEO/GEO friendly since search engines like Google can crawl and index all URLs available in the DOM. However, the major issue is the performance and page load time.I’m looking for suggestions on how to improve the page performance without negatively impacting SEO/GEO. We are also considering approaches such as pagination or a “Load More” option. Thanks in Advance.RegardsVeera

The sling:configs node is created and the enabled property is set to true for the node com.adobe.cq.wcm.core.components.internal.DataLayerConfig for the given site. The PDFs are loading from the Adobe embed component that cretaes PDFs using iframes. How to fetch events int the data layer?

I am working with developers to implement UE in our AEM cloud instance, without EDS and not using a headless architecture. They have told me that to work with UE we will need to direct users to a specific URL, and NOT use the convenient UE entry point that Adobe provides on the landing page (the one where you just input the site URL).So far, efforts to get components working smoothly have only succeeded if we use the other URL format. Has anyone else encountered this limitation? If business users have to enter a particular URL formula for getting to UE with the page they want, it’s going to be messy. The AEM input field for easily entering UE and navigating within it would be perfect, but if our devs are correct, doing it this way means glitches and limitations.Thanks for any advices.

BackgroundWe are building an automated content sync pipeline on AEM as a Cloud Service that reads product data from an external PIM system (Salsify) and manages Content Fragments and Product Detail Pages on AEM Author.We have three Adobe App Builder actions deployed on Adobe I/O Runtime that together manage the full product content lifecycle: Action What it does AEM credentials used Product Sync Fetches all products from the PIM channel export and upserts them as AEM Content Fragments (create or update). Includes a duplicate activation guard to prevent concurrent executions. IMS OAuth (CF Management API) PDP Page Creation Reads synced parent Content Fragments, filters to those flagged for web publication, and deletes + recreates their Product Detail Pages on every run IMS OAuth + AEM Developer Console JWT Orphan Cleanup Detects CFs and PDP pages in AEM whose products no longer exist in the PIM feed and deletes them. Supports two modes: single SKU (fast, no PIM API call

We are looking to copy content between two environments across different AEM as a Cloud Service programs, such as from Environment A in Program A to Environment B in Program B.We explored the Content Copy feature and can see the “Destination Program” option. However, after selecting the destination program, we are still able to see only the source program environments.Is cross-program content copy currently supported? If yes, are there any prerequisites or additional configurations required for destination environments to appear?

Hi Everyone,I am working on Dynamic Media integration in AEM as a Cloud Service using the AssetDelivery API.Currently, my Sling Model generates URLs like:/adobe/dynamicmedia/deliver/dm-aid--e3ba909d-36de-46ea-ba72-bd8737f9c61f/OIP.jpeg.webp?preferwebp=trueusing:assetDelivery.getDeliveryURL(assetResource, options);However, from the AEM Assets Console, I can see URLs in the following format:/adobe/assets/urn:aaid:aem:20c84486-5512-4ac8-b8f7-a8ba2c735155/as/OIP.avif?width=1024&quality=65&assetName=OIP.jpegMy understanding is:/adobe/dynamicmedia/deliver/... → Scene7 / Dynamic Media Deliver URLs /adobe/assets/urn:aaid:aem:... → Dynamic Media with OpenAPI (Next-Gen DM) URLsI want to understand:Can AssetDelivery#getDeliveryURL() generate the OpenAPI-style /adobe/assets/urn:aaid:aem:... URLs? If not, what is the recommended API/service to generate those URLs programmatically inside Sling Models? Is additional OpenAPI configuration required in AEM Cloud Service to expose asset URNs/asse

Technology and Digital Transformation

AEM Sites Developer Professional free online training with exam preparation. Have a question about the AEM Foundations course, AEM Sites Developer Professional course, or the Certified Professional exam prep guide listed on the certification information page? Reply to this thread and a learning support specialist will respond to you.  We follow the Adobe Experience League Community Forum Guidelines in this discussion thread. If the response resolves your question, consider giving a Like to the learning specialist who replied. We appreciate the kudos! Questions outside the scope of the online courses and exam preparation guide will be directed to the main community forum page. 

Hi,I need to move a page to a folder in groovy script and it does not work.Instead of moving the Page to a Folder that exists it moves the page to the same original folder with a name archive1, archive2 etc.I basically want to write in the groovy script the function tha is the same as the move in the AEM Editor Page srcPage = pageManager.getPage(srcPath) if (!srcPage) { return buildResult(lineNo, srcPath, destPath, "ERROR", "Source page not found!") } def pageName = srcPage.getName() try { if (!dryRun) { pageManager.move(srcPage, destPath, pageName, true, true, null) } return buildResult(lineNo, srcPath, destPath, "SUCCESS", dryRun ? "Would be correctly deactivated and moved" : "Deactivated and moved") } catch (Exception e) { return buildResult(lineNo, srcPath, destPath, "ERROR", "Move Error: ${e.message}") } 

 Headless using AEM Sites, not only Content Fragmentsby @daniel-strmecki Introduction Headless delivery in AEM is often associated with flexibility, performance, and modern frontend architectures. For developers, this usually sounds like a clear step forward. However, in many enterprise projects, headless has also introduced a major tradeoff: marketers and content authors lose access to many of the AEM Sites features and the familiar WYSIWYG editing experience they rely on every day.This is why "headless AEM" is still too often reduced to "Content Fragments exposed through GraphQL APIs". Content Fragments are powerful and absolutely have their place, but they are not the only way to build headless experiences with AEM. At least not anymore.With AEM as a Cloud Service, AEM Sites, and the Universal Editor, we can now take a more balanced approach: keep enterprise-grade content management and visual authoring in AEM Sites, while delivering experiences through a modern headless frontend ar

We have a fully functional React SPA - it is standalone and not part of the Adobe architecture.  A portion of the same website does utilize AEM to serve its content.  The business would like to be able to personalize some content utilizing AEM and publish that as content on a React page/route.  What is best practice to going about this?  Some of the content may be dynamic based on some data that the React SPA fetched from an API as well.

In many enterprise environments, AEM is the backbone of digital experience delivery—powering critical customer journeys across channels. While much of the focus is often on content and features, I’ve found that operational excellence is what truly unlocks AEM’s full potential. Over the past year, my focus has been on shifting AEM operations from a reactive support model to a more proactive and predictive approach. The ChallengeLike many organisations, we faced common challenges:Limited visibility across AEM, APIs, and downstream systems Longer troubleshooting cycles due to fragmented logs Reactive incident handling impacting business SLAs These challenges highlighted a key gap—not in capability, but in end-to-end observability and operational alignment. The Approach To address this, we focused on three key areas:1. End-to-End ObservabilityWe integrated monitoring across AEM, dispatcher, and backend services to gain a single view of system health. This significantly improved our ability

We are excited to announce our Adobe Experience Manager Champion of the Month for May, ​@VidyR​!  Vidy was a clear choice for this recognition, as she truly embodies the spirit of the Adobe Champion Program. Not only does she actively raise her hand to support key initiatives like speaking on our upcoming Champion Application webinar, writing articles on Perspectives, and sharing feedback with our AEM Assets Product teams, but she regularly attends AEM Champion social events and fosters relationships outside of programming. She is a rising star in our community, and the program wouldn’t be the same without her bright personality. Thank you, Vidy, for your leadership and commitment to the Champion Program!  

Hi Team,I'm currently working on a custom component in AEM as a Cloud Service.In the Rich Text Editor (RTE) field of my dialog, when switching to source edit mode (HTML view), I noticed that plain text input is automatically wrapped with <p> tags. For example:Input:Hello WorldOutput:<p>Hello World</p> I would like to disable this behavior so that plain text remains unchanged, without being wrapped in <p> tags. Is there any configuration available to prevent automatic <p> insertion in source mode?Or would this require a custom plugin or overlay? Thanks in advance for your help!