Unable to provide permission to user for oak:index in publish instance | Community
Skip to main content
Level 2
November 29, 2017
Solved

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

  • November 29, 2017
  • 5 replies
  • 1387 views

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.

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 joerghoh

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

5 replies

joerghoh
Adobe Employee
Adobe Employee
November 29, 2017

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

Level 2
November 29, 2017

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.

joerghoh
Adobe Employee
joerghohAdobe EmployeeAccepted solution
Adobe Employee
November 29, 2017

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

Level 2
November 30, 2017

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

joerghoh
Adobe Employee
Adobe Employee
November 30, 2017

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

Jörg