Jcr Package Manager not working | Community
Skip to main content
Level 2
November 17, 2023
Solved

Jcr Package Manager not working

  • November 17, 2023
  • 1 reply
  • 793 views

Hi,

 

We have a requirement to create a packages whenever we trigger a servlet. It works fine when I use request.getResourceResolver() but when I try using resourceResolver created from subservice. it always fails. Gives a PathNotFoundException "Node with path '/' not found".

 

Couple of references which I found:

https://github.com/Adobe-Consulting-Services/acs-aem-commons/blob/master/bundle/src/main/java/com/adobe/acs/commons/packaging/impl/InstantPackageImpl.java

https://www.albinsblog.com/2018/01/sling-scheduler-to-auto-create-packages-JcrPackageManager-api-aem.html

 

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Mir_Rayan

Hi @omkarmanasba 

 

You will need to provide read permissions to  "/ " level.

 

If your service user is part of the group "everyone" then it should have this permissions. 

 

 

I assume you are trying in your local environment, thus you dont have "everyone" group assigned. 

 

additionally, you will also need to give read create and modify permission to your package group. for example "/etc/packages/{your_group_name}" 

1 reply

Mir_Rayan
Mir_RayanAccepted solution
Level 2
November 17, 2023

Hi @omkarmanasba 

 

You will need to provide read permissions to  "/ " level.

 

If your service user is part of the group "everyone" then it should have this permissions. 

 

 

I assume you are trying in your local environment, thus you dont have "everyone" group assigned. 

 

additionally, you will also need to give read create and modify permission to your package group. for example "/etc/packages/{your_group_name}" 

Level 2
November 17, 2023

everyone group was assigned. Respective permissions for /etc/packages were applied. Still there was a deficiency in root read privileges. Either way thanks for the answer. It worked after I gave the read permission to root manually for the respective system user