CAConfig Editor not working in AEMaaCS


The caconfig editor isn't working in AEM as a Cloud Service. More specifically, there seems to be a problem with the clientlibs for the editor.

I've discovered that it works when you delete the longCacheKey property from the two clientlibs, as can be seen here: AEMaaCS seems to create its own hashed cache key then. However, I guess this is not a solution for on-premise AEM installations, so not sure what the best solution would be...


Stefan Seifert
July 7, 2020, 2:58 PM

sounds good! next regular release is planned in this week or early next week

Jan Delannoy
July 7, 2020, 2:53 PM

Tested it with the latest 1.7.3-SNAPSHOT on AEMaaCS 2020.7.3831.20200702T194958Z and I can confirm that it works. Thanks!

Stefan Seifert
July 7, 2020, 1:42 PM

i've already changed in on the develop branch

you can give it a try with snapshot 1.7.3-SNAPSHOT

Jan Delannoy
July 7, 2020, 1:37 PM

I’m on the same version (2020.7.3831.20200702T194958Z), not entirely sure if I tested if with 2020.6.3800.20200626T210738Z as well…. In any case, indeed I would expect it to work with a longCacheKey set as well, as it should take precedence over the other configuration. Anyway, I will create a pull request then for that small fix.

Stefan Seifert
July 7, 2020, 1:24 PM

which AEM cloud version do you have in use? i've just retested it with 2020.7.3831.20200702T194958Z and i can reproduce the that the display is broken - last time it tested it was a few days ago.

i'm aware that setting a longCacheKey is no longer required in aem cloud service, but last time i tested it worked also if one was set.

anyway it think it's not required to have a longCacheKey set for a clientlib that is only used on the author, and we can just remove it also for onprem installations.



Stefan Seifert


Jan Delannoy