Hi Marco
Yeah... no, that's not how the default authorisation model works :-)
But obviously you would be able to write and deploy your own authorisation
model that just behaves as you expected it to work.
Some hints can be found at
http://jackrabbit.apache.org/oak/docs/security/introduction.html
Hi Angela,
thanks for the answer. I thought (and I was wrong) that the user that
created a node would have had complete control on it (and not just the
permissions explicitly granted to him). That's why my question... thanks
again for the clarification.
Marco.
On Wed, Feb 14, 2018 at 9:47 AM
Hi Marco
It depends a bit on how you originally setup the 'ownership' in the first
place.
- if you have granted permissions to userA _on_ that very node, you can
simply remove the entries and create new ones for the new owner.
- if you have granted permissions to userA on a _parent_ node you can
