Grouper Developers Forum

[Chris Hyzer <>]

Do you think we should add an entry on the roadmap to have attribute framework / permissions management (i.e. setting up the definitions, name, and inheritance) in WS.  You can already (un)assign/read via web service, but I think it is common to have dynamic permission resources that aren’t managed by the Grouper UI.  i.e. if managing a file system, and someone creates a folder, something needs to create that resource, and setup its inheritance.  I think there could be a lot of operations here J  maybe we need to prioritize…

 

1.       Create/update attributeDef (I guess this includes actionList?)

2.       Delete attributeDef

3.       View attributeDef

4.       Create/update attributeDefName

5.       Delete attributeDefName

6.       View attributeDefName

7.       Create/delete action inheritance

8.       View action inheritance

9.       Create/delete resource inheritance

10.   View resource inheritance

11.   Create/delete role inheritance

12.   View role inheritance

13.   Are attribute privileges available on WS?  I forget.  If not, add

 

To satisfy the common use case (e.g. PSU file system), then #4, 5, 6, 9, 10 are the only ones required, maybe those should be prioritized higher.

 

 

Thanks,

Chris