Menu ▾ ▴

#21 security improvements

open
nobody
Core (9)
3
2012-09-17
2003-03-07
Per Nyfelt
No

Today security constraints can only be set on the
object level.
To get method level security you would have to
intercept all access with your own security class that
authenticates your credentials and allows or denies
requests which means you could no longer access your
object directly...

It would be better to do something real with security.
We could create an JAAS implementation and create a
Principal when we do Object lookup. Then we equal our
groups with the role concept in JAAS so that you could
do both programmatic and declarative security.

programmatic as in

if (database().user().isCallerInRole("myGroup")) {
// do stuff
}

and declarative as in specifying it in the ozone class
descriptor (ocd file)
maybe with something like:

<ozone-class-descriptor>
<name>AutoImpl</name>
<superclass>org.ozoneDB.OzoneObject</superclass>
<interface>Auto</interface>
<constructors>
<publicConstructor/>
</constructors>
<methods>
<publicMethod>
<name>equals</name>
<parameter>java.lang.Object</parameter>
<locklevel>READ</locklevel>
<security>
<group>myGroup</group>
<group>administrators</group>
</security>
</publicMethod>

Discussion


Log in to post a comment.