The goal is to handle security on Directory access.
Global security
Directory descriptor should allow to specifiy some simple security restrictions:
<directory name="foo"> ... <permissions> <permission name="Read"> <user>readerUser</user> </permission> <permission name="Write"> <user>superUser</user> </permission> <permission name="Write"> <group>mygroup2</group> </permission> </permissions> ... </directory>
Having READ is included in WRITE.
If no restriction is set on the directory descriptor, then default is :
- READ : EVERYONE
- WRITE : Administrators, powerusers
This default setup is consistent with the check we are already doing in the Automation and REST endpoints.
Entry level checks
For some specific cases, we may want to have a per-entry check, at least for WRITE access.
ex : Power Users should not be able to edit admin accounts
For this of use case, we could introduce a kind of Directory SecurityPolicy DirectoryEntrySecurityManager.
For Repository backed Directories, the implementation could be ACL based, and we can define other implementation for specific directories.
- depends on
-
NXP-15731 Directories should throw a security exception on denied access
-
- Resolved
-
-
-
- Resolved
-
-
NXP-15737 Rely on standard filters to perform directory security checks
-
- Open
-
- is duplicated by
-
-
- Resolved
-
- is required by
-
-
- Resolved
-
-
-
- Resolved
-
-
NXP-15653 Add security checks at directory entry level
-
- Open
-
-
-
- Open
-
-
-
- Open
-