Sling context aware configuration
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.
If sling context aware configuration used to provides the configuration for anonymous user content and the configuration is working on author environments but not on publishers or live site then
Make this configuration available for anonymous user, user has the read permissions on AEM server from which the content is being served.
In most of the AEM projects these configurations stays under conf path: /conf/<siteName>/sling:configs/<configuration>
To make this config available to anonymous users, everyone group must have the read ACL on AEM publisher server for above configuration path as any user will be a part of the everyone group on AEM by default.
AEM does not provide any default interface or console to edit/update the sling context aware configurations
By defining a property sling:configPropertyInherit on the configuration resource, property merging is enabled between the current configuration resource and the next resource with the same name (singleton or resource collection item) in the configuration resource lookup order. In general next resource means the configurations available at /global folder
Properties that are not defined on the current configuration resource are inherited from the /global resources and a merged value map is used for the configuration mapping.
By setting the property sling:configPropertyInherit on multiple configuration resources that are part of the lookup order it is possible to form deeper inheritance chains following the same rules
If sling:configPropertyInherit property is missing from current resource then AEM won't resolve/merge the properties from the global folder configuration.