Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

Unable to provide permission to user for oak:index in publish instance

Avatar

Level 2

Hi team,

I am creating a new user for deployment purpose in publish instance. While providing permissions, while giving read access to oak:index and save , it is not saving the permission. A pop up box with blank content is appearing and even in logs there is no error. Please Help.

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

Does this deployment user has write permissions to /oak:index?

Additionally: I would still give you the advice to use the "admin" user for deployment, it makes a number of things much easier (for example you don't have to debug why writes to /oak:index do not work). And if you automate your deployment, you also get rid of a large amount of typical error cases during deployment.

Jörg

View solution in original post

5 Replies

Avatar

Employee Advisor

Deployment is for me one of the rare cases, where there is no other way than to use the "admin" user. Sometimes it's not even sufficient to provide all privileges on /, but you need to grant additional permissions, for example to create node types. When you get at this point, it's much easier to use the "admin".

Jörg

Avatar

Level 2

Hi Jorg,

It is recommended in our project not to use admin credentials. Hence we are creating new user for deployment purpose. Can you please let us know where we can check the logs for root cause of not able to give permission to oak:index.

In Author instance , we are able to create the user and give permissions whereas in publish instance we are not able to provide permission for oak:index.

Avatar

Correct answer by
Employee Advisor

Does this deployment user has write permissions to /oak:index?

Additionally: I would still give you the advice to use the "admin" user for deployment, it makes a number of things much easier (for example you don't have to debug why writes to /oak:index do not work). And if you automate your deployment, you also get rid of a large amount of typical error cases during deployment.

Jörg

Avatar

Level 2

Hi Jorg,

we are unable to provide write/ read permission to /oak:index. We are getting a blank pop up when saving the permission. I have suggested to use admin for our client, however we want to give a try why we are not able to provide read/write permission to oak:index.

Thanks,

Vidhu

Avatar

Employee Advisor

/oak:index is a regular JCR node, where you can apply ACLs. I do not expect problems when setting permissions there.

Jörg