-
1. Re: Permissions list for project
tausuahmed Dec 12, 2010 10:39 AM (in response to zenig.szimmerman.sunshineradiology.com)Hi,
Try persistantBasedPermissionResolver and use Permission (User/Role) class for storage.
try http://java.dzone.com/articles/acl-security-in-seam
Thanks,
Tauseef -
2. Re: Permissions list for project
zenig.szimmerman.sunshineradiology.com Dec 12, 2010 10:56 AM (in response to zenig.szimmerman.sunshineradiology.com)I have already setup a persistent permission resolver and it works well. At this point, I am looking for a simple way to manage application permissions via views.
If you look at the bottom of page 3 of the above article, this summarizes what I want to accomplish:
look at how we can create permission management views to more easily manage our object permissions through a nice user interface.Unfortunately I can't find
ACL Security In Seam, Part 2
published anywhere! -
3. Re: Permissions list for project
shane.bryzak Dec 12, 2010 6:41 PM (in response to zenig.szimmerman.sunshineradiology.com)Unfortunately I didn't get around to writing Part 2 as that was around the time we decided to investigate using PicketBox/PicketLink to provide ongoing security features for Seam.
As for your issue, I'm assuming you have a UserPermission table etc in your application which you use to store your permissions. There's nothing stopping you from creating a view that reads the records directly from this table, without going through the PermissionManager API. That is the approach that I would recommend to create a view that displays all permissions.
-
4. Re: Permissions list for project
zenig.szimmerman.sunshineradiology.com Dec 13, 2010 11:48 AM (in response to zenig.szimmerman.sunshineradiology.com)I am looking forward to understanding PicketBox/PicketLink in Seam 3!
I do have a UserPermission table built into the application. I can query that table directly for assigned permissions, however, it is assuming that at least one roles/user possess all possible permissions.
I may end up creating a separate table holding all possible permissions and allowing a view to assign those permissions to either a role or user.
It got me going in the right direction. Thanks.