Sling is the key framework being used in AEM architecture which provides the feature of configuration specific to context which means it is possible to use the different configuration for the set of pages from the content repository which will allow you to delivery the personalized digital experiences based on the context of content.

Key issues with ca-configs:

• Configuration working on author environments but not on publishers or live site

  • Sling context aware configuration is meant for the configuration for content which user will access as a anonymous user.

  • To make this configuration available for anonymous user, He should have the read permissions on AEM from where the content is being served.

  • In most of the AEM projects these configurations stays under path something like: /conf/<siteName>/sling:configs/<configuration>

  • To make this config available to end users, everyone group must have the read ACL on AEM publisher for above configuration path as any user will be a part of the everyone group on AEM by default.