OAK-11733: Adding information to access denied

[Amoratinos]

When getting an access denied exception it's hard to identify the path and what was the options evaluated.

[anchela]

lgtm

[cschneider]

lgtm

[reschke]

@anchela - did you consider whether this could disclose information that the caller shouldn't get?

[Amoratinos]

To my understanding it shouldn't be any risk as it's only revealing the path. Initially more information was exposed like the actions or the permissions requested but that was removed.

In my opinion, the method we should pay the most attention to is the one that receives the tree, the property state, and the actions, since this is the one used in multiple places. This checkPermissions is used on NodeImpl.addNode removeMixin addMixin methods and in ImporterImpl.createTree. The only scenario where I could foresee a risk is when the path of a node is used like an ID, e.g. node path represents a token or sth like, and I think that's an edge case.

[anchela]

@reschke , i looked at all instances where the methods are being called today and didn't find how they would reveal the existence of a path it it would happen with itemExists or in the permissionvalidator.
if you happen to find a case, i am happy to be proven wrong.

having said that:
please check as well.... will wait for your explicit approval before merging it