This doesn't resolve the JWT token/AEM scope setup. If we login and generate JWT token from one server, how can AEM as second server to retrieve the JWT token and use any library(jsonwebtoken? or AEM oauth client) to validate, if success, get user's some profile to map using scope to authorize the u...

Also, the guideimage in XML works fine in DEV, but not in PROD.  

Hi, we have a AEM adaptive form in 6.5.8, everything works fine on dev. But when we package everything and deployed to PROD, the header defined in form tempate shows up at the bottom of the form. We compared the content.xml line by line for all the forms/fragments/folders, other than replication sta...

WKND has no problem. Just one experience fragment can be targeted. How can I know why other components cannot be targeted. For example: on: http://localhost:4502/content/wknd/language-masters/en/magazine/arctic-surfing.html Only  /content/experience-fragments/wknd/language-masters/en/contributors/ja...

Hmm, seems AEM classic, from 6.5.8 to 6.5.15, WKND classic 2.1.2 works, at least the target button for each component showed up. For the cloud version 2022.10.9398.20221020T071514Z with WKND 2.1.2(not the classic version), the target button for each component doesn't work.

No matter Adobe Cloud v2022.10.9398.20221020T071514Z or 6.5.14, the WKND doesn't work for me. At the same time, the we-retail is working fine on the same 6.5.14. Also, I read and follow the document again and again, really cannot find where to start troubleshoot.

I added the brand and activity. the "Starting Targeting" button is working now. However, still, for component, I didn't see the target button.

I can see the contexthub in preview. However, when I go to targeting mode, the "Start targeting" button is disable? The contexthub is in the page custom header sling code and all the context hub default setting seems fine. See images below. "Start Targeting" is disabled. I am using the release 2.1.2...

What's the difference between page and page/jcr:conent? When I access .../pagex.model.json and .../pagex/jcr:conent.model.json, I only see the jcr:conent.model.json has the allowedComponents section, while the page model.json doesn't. What's the scenario need to access the jcr:content node instead o...

Both LC and AEM are working fine on DEV so far. Will test next Tuesday to advance the time to Jan 9 on DEV to see if anything breaks after Jan 8.