Task #180 (closed)
Implement 64-bit Permissions and set to "not null"
| Reported by: | jamoore | Owned by: | jamoore |
|---|---|---|---|
| Priority: | major | Milestone: | 3.0-M3 |
| Component: | Security | Version: | 3.0-M3 |
| Keywords: | store114, permissions,iteration1 | Cc: | |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description
The Permissions field has been ignored up to this point. Starting in M3 it will become active (set to not-null) and initial values will be provided according to a properties file (See #179).
Logic for testing certain functions canRead, canWrite, etc. may should end up in ome.model.internal.Permissions, though if all logic is pushed into the DB (see #117), then perhaps it lives there.
Initially, the upper 48-bits of Permissions won't be used. The lower 16 defining:
----rwx-rwx-rwx-
For later use of the upper 48-bits, a script/task using the Hibernate StatelessSession? is probably in order.
Change History (5)
comment:1 Changed 18 years ago by jmoore
- Resolution set to fixed
- Status changed from new to closed
comment:2 Changed 18 years ago by jmoore
- Keywords iteration1 added
comment:3 Changed 18 years ago by jmoore
r784 fixes a bug in the bit definitions of Permissions
comment:4 Changed 18 years ago by jmoore
comment:5 Changed 18 years ago by jmoore
r830 defines an immutable wrapper around Permissions so that public final static Permissions constants can be defined on the class. One Permissions.DEFAULT is now set in mapping.vm to be used in all new object model instances.
r764 implements permissions. They are now persisted to the database and can be set by users. (They are never null). Other tickets like #179 (configuring umasks) and #200 (read access control) will take care of further permissions aspects.