We faced an issue while doing AEM upgrade from 6.1 to 6.3 instance. We had a system user who needed to be provided read permissions on /apps . We had added the rep:policy node xml of /apps in the source code which contained the read access of the system user on /apps node , and used
<acHandling>overwrite</acHandling>
in the maven vault package plugin that deployed the rep policy node to any new instance/environment. This way we don't need to worry about the system user's permission in any new created environment/instance, since it part of the code.
But after upgrading to AEM 6.3, none of the we-retail pages and our site's page worked, after removing all entries from filter.xml and adding the one by one, it was found out that the issue was due to our /apps/rep:policy node replacing AEM 6.3's default rep:policy.
How can we better handle it? Should the rep:policy node never be part of the code, as this will be an issue again when upgrading to another instance of AEM?
