Re: Pattern Approach to User permissions?
Re: Pattern Approach to User permissions?
- Subject: Re: Pattern Approach to User permissions?
- From: Daryl Thachuk <email@hidden>
- Date: Tue, 2 Mar 2004 22:29:20 -0700
Using JAAS in WO takes a bit of coding but it is not that hard. The
hardest part is writing the Custom Policy and getting the app class
permission files to play nicely. In a previous life I wrote a reusable
JAAS based security framework for EO's and it worked quite nicely.
If you need any help, let me know.
-d
------
Daryl Thachuk
Montage Technologies Inc.
http://www.montagetech.com
On Mar 2, 2004, at 6:07 PM, Arturo Pirez wrote:
On Mar 2, 2004, at 4:45 PM, Kieran Kelleher wrote:
I am trying to decide how best to incorporate user-based permissions
for selecting (viewing), inserting (adding), updating (editing) and
deleting EO's into my object model design.
I'm also wrestling/designing such a system. I've decided to pattern
mine after JAAS but beyond that I'm not certain how to proceed.
In JAAS you have a Subject toMany Principal toMany Permission. In
both your and my model that falls short in that we both want to manage
Resources. A Subject is, essentially, a collection of Principals.
Each Principal can be interpreted as a role of some sort (kind of like
group permissions). In the base JAAS model, a Permission includes a
kind of Resource class and an action that can be performed against it.
There are examples of how to extend JAAS to include resource
instance-based information. See this document over at IBM
http://www.ibm.com/developerworks/java/library/j-jaas/. In any case,
the JAAS arena may give you some ideas on how to proceed.
In my case, I'm not sure that I want the coupling between the
permissions model and my other models that you're thinking about. I
want my security framework to be reusable to other applications as
well. What I would like would be to use something like eogenerator to
create java.security.Guard-wrapped EOs. Does anyone know if it can be
modified to do so? Alternatively, make a subclass of EOGenericRecord
that overrides the validate methods to enforce permissioning. Then I
figure I'll need a permission/security oriented version of
WOComponentContent to wrap around things.
Thoughts?
----
WO in philadelphia - wanna cheesesteak with that?
Please visit webobjects.meetup.com.
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.