The following section provides answers to Frequently Asked Questions (FAQs) related to Screens as a Cloud Service project.
AEM as a Cloud Service changes the long cache keys with every deployment. AEM Screens generates the offline caches when the content is modified, rather than when the Cloud Manager runs the deployment. These long cache keys in the manifests are invalid, so the player fails to download these clientlibs.
longCacheKey="none" in your
clientlib folder removes the long cache keys altogether for these clientlibs.
Offline caches are generated using bulk-offline-update-screens-service service user. Certain paths, not accessible by
bulk-offline-update-screens-service, lead to missing content in offline manifests.
In your code, that is,
ui.config or ui.apps, create an OSGi configuration in configuration folder, with the following content, and title the file name as
scripts=[ " set principal ACL for bulk-offline-update-screens-service allow jcr:read on /content/mysite allow jcr:read on /apps/my-resources end "]
It is recommended to use images in the format
.jpeg in an AEM Screens as a Cloud Service channel, for the best digital signage experience.
The images in the format
*.tif (Tag Image File format) are not supported in AEM Screens as a Cloud Service. In case, if a channel has this format of image, then, on the player side, the image will not be rendered.
It is recommended to leverage AEM Screens caching capabilities, but if you need to run your Channel in Developer mode and the AEM Screens Player shows a blank screen, check your Player’s developer tools and look for
frame-ancestors errors. The resolution is to configure the dispatcher to allow content running in iFrames. Usually the following configuration will work:
Header set Content-Security-Policy "frame-ancestors ‘self’ file: localhost:*;"
As a best practice, you can limit the registration code usage. If a registration code is compromised, but has a limit of 100 registrations, then the attacker can register only up to that number, but not more. You can always update the usage limit after the registration code is created and some of the customer’s players have already been registered. If the customer observes unusual registration activity for a specific registration code, they can lower the limit in real-time while they investigate and can increase the number back if it was a false alarm, without impacting the already registered players.