Grouper Developers Forum

[Chris Hyzer <>]

Two side effects of this…

 

1.       You can list all the applications that use the authorization system (service registry).

2.       A person can go and see what applications they have access to… maybe we could have links to the start page of the apps too…

 

Thanks,

Chris

 

From: Chris Hyzer
Sent: Thursday, August 04, 2011 12:32 AM
To: 'Grouper Dev'
Subject: domain added to roadmap?

 

I think it would be useful for Grouper to have a “domain” tag which could be attached to groups/permissions/etc or used in configs etc.  The domain would be similar to an application or a group of applications. 

 

The end result is that someone could be linked to the UI with the domain in the URL, and they would see the groups/folders/permissions/instructions/etc that are relevant to that domain.  Or in the WS, the client could request memberships for a user relevant to a domain, and if groups/roles/permissions were added after the application was coded, they would be return based on domain.  Maybe it would also filter the subjects returned in subject searches.  E.g. an application that has nothing to do with prospective students or alumni should not return those subjects in subject searches.

 

Note that it is currently a type of attribute definition: domain.  Currently it is not used, but I picture it being a marker attribute with no value, perhaps with restrictions on which types of objects it can be assigned to: group/role, folder, attributeDef/permissionDef…  and like limits there are other configs or rules that are used for domains…

 

If you are interested in this, or have other ideas about it, let us know.

 

Thanks,

Chris