Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Field level security

See original GitHub issue

Many users ask for field-level security. This is not supported by OrientDB, but it could be done in the same Security hook. This is my initial proposal:

We can store authorization in ORole in the format: property.<class-name>.<field-name> = CRU
On read if no “R” permission is set, we could just remove the field. On update of document we should merge new content with existent one to avoid non accessible fields are removed
On update if no “U” permission is set and the field arrives as changed, then a OSecurityException is raised
On create if no “C” permission is set and the field arrives as filled, then a OSecurityException is raised

Issue Analytics

State:
Created 8 years ago
Comments:10 (4 by maintainers)

Top GitHub Comments

1reaction

laacommented, Aug 6, 2021

Hi @kbrandwijk . We are not going to implement this feature in foreseen future. We have added predicate based security and thinks that set of security features is not needed to be extended.

1reaction

lvcacommented, Mar 28, 2018

This issue has recently got the interest from an OrientDB client that is evaluating of sponsoring it. We should have news in the next week. I keep you posted.