OakAccess:0000 Access Denied for Package Manager build step.

Avatar

Avatar
Validate 10
Level 2
fionas76543059
Level 2

Likes

3 likes

Total Posts

74 posts

Correct reply

1 solution
Top badges earned
Validate 10
Validate 1
Boost 3
Boost 1
Applaud 5
View profile

Avatar
Validate 10
Level 2
fionas76543059
Level 2

Likes

3 likes

Total Posts

74 posts

Correct reply

1 solution
Top badges earned
Validate 10
Validate 1
Boost 3
Boost 1
Applaud 5
View profile
fionas76543059
Level 2

04-02-2021

hi guys,

 

I need to have read/create access for package manager on a prod machine but not build or install access. I sent the instructions below to my boss and she said she did them. However, although I can see Package Manager UI and create a package with filters etc. and do a Build, at the last minute it fails with the above OakAccess problem. What should I do extra ?

thanks

Fiona

 

 

Is this info still up to date for 6.5 AMS ? 

 

"Permissions needed for using the Package Manager

To grant users the right to create, modify, upload, and install packages, you must give them the appropriate user/group page permissions at the following locations:

 
 (give Read/Create  but excluding Modify/Delete as these would give them Install permissions.)
 

- /libs/cq/core/content/nav/tools/deployment

- /libs/cq/core/content/nav/tools/deployment/packages

- /etc/packages

 

Solved: AEM 6.3 package permissions: allowing a user group... - Adobe Experience League Community - ...

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Boost 500
MVP
Vijayalakshmi_S
MVP

Likes

573 likes

Total Posts

728 posts

Correct reply

240 solutions
Top badges earned
Boost 500
Give Back 50
Give Back 5
Ignite 10
Ignite 5
View profile

Avatar
Boost 500
MVP
Vijayalakshmi_S
MVP

Likes

573 likes

Total Posts

728 posts

Correct reply

240 solutions
Top badges earned
Boost 500
Give Back 50
Give Back 5
Ignite 10
Ignite 5
View profile
Vijayalakshmi_S
MVP

04-02-2021

Hi @fionas76543059,

Permissions related to Package manager still applies. Cross check if you have permissions for the node/filter contents as well in addition to (/etc/packages)

https://experienceleague.adobe.com/docs/experience-manager-65/administering/contentmanagement/packag...

Answers (1)

Answers (1)

Avatar

Avatar
Boost 3
Level 1
shashim1223
Level 1

Likes

3 likes

Total Posts

5 posts

Correct reply

0 solutions
Top badges earned
Boost 3
Boost 1
View profile

Avatar
Boost 3
Level 1
shashim1223
Level 1

Likes

3 likes

Total Posts

5 posts

Correct reply

0 solutions
Top badges earned
Boost 3
Boost 1
View profile
shashim1223
Level 1

04-02-2021

@fionas76543059 Ca you share your activity log from crx/packmgr view where exactly it failed. Do you have enough read access to filters path tree you added to package?