When page is renamed/move the references are not updated

Description

Context
When a page is moved or renamed and is referenced in a pathbrowser widget (https://wcm.io/caconfig/editor/usage.html#pathbrowser) inside a configuration below /conf will not be updated. This is caused because the OOTB service user called "reference-adjustment" has no rights in the /conf folder and then can't find & update the properties.
This will be easy to fix by modifying the configuration
"org.apache.sling.jcr.repoinit.RepositoryInitializer~reference-adjustment"

Expected result
The references to the page should be properly updated

Activity

Show:

Stefan Seifert August 25, 2021 at 4:08 PM

yes, got the same reference today - let's wait then

Pablo Castelo August 25, 2021 at 2:16 PM

I also raised an Adobe Support ticket and I got an answer

The following Jira ID represents this use case and is already in Engineering's ToDo list: #SITES-1350 - Assets used in a Template are not automatically adjusted when modified.

I think with that information we can close this defect and wait for the fix in future SP.

Stefan Seifert August 19, 2021 at 3:51 PM

makes sense - but we will not add custom ACLs like this to the deployment package of the caconfig editor or extensions - the administrator of the AEM instances should have full control over the ACLs.

but i still think this is a common use case which should be fixed in AEM itself (and your set of ACLs is only a workaround that can be applied until this is fixed). for example, create a structure component in an editable template and assign an asset to it. if the asset is moved, the references is not updated, image reference is broken.

we have the same requirement for on of our projects, i’ve created an adobe support ticket.

Pablo Castelo August 13, 2021 at 11:24 AM

Not sure if should be modified by Adobe because in an OOtB instance that permission is not needed. That’s the reason because I open the ticket here.

To fix it it’s quite straightforward, just include the configuration in the package

org.apache.sling.jcr.repoinit.RepositoryInitializer~reference-adjustment.config

it should contain the OOtB rows and the custom one that we need
scripts=[
"set\ ACL\ for\ reference-adjustment-service\r\nallow\ jcr:read,jcr:modifyProperties\ on\ /content\ restriction(rep:glob,//jcr:content)\r\nend",
"set\ ACL\ for\ reference-adjustment-service\r\nallow\ jcr:read,jcr:modifyProperties\ on\ /content\ restriction(rep:glob,//jcr:content/)\r\nend",
"set\ ACL\ for\ reference-adjustment-service\r\nallow\ jcr:read\ on\ /etc\r\nend",
"set\ ACL\ for\ reference-adjustment-service\r\nallow\ jcr:modifyProperties\ on\ /etc\ restriction(rep:glob,//jcr:content)\r\nend",
"set\ ACL\ for\ reference-adjustment-service\r\nallow\ jcr:modifyProperties\ on\ /etc\ restriction(rep:glob,//jcr:content/)\r\nend",
"set\ ACL\ for\ reference-adjustment-service\r\nallow\ rep:write\ on\ /content/usergenerated\r\nend",
"set\ ACL\ for\ reference-adjustment-service\r\nallow\ jcr:read,jcr:modifyProperties\ on\ /content/dam/collections\r\nend",
"set\ ACL\ for\ reference-adjustment-service\r\nallow\ jcr:read,jcr:modifyProperties\ on\ /conf\ \r\nend", \

]

Stefan Seifert August 13, 2021 at 10:55 AM

you’re right - i can reproduce the problem.

however, this is not a problem that can be fixed within the config editor implementation / deployment package.

recent AEM versions (6.4/6.5/AEMaaCS) are using a service user “reference-adjustment-service”, and this comes preconfigured OOTB with AEM. i think a Adobe support ticket should be created to change the default configuration of it?

how did you fix the ACLs of this service user in your environment in a reliable way?