(Upcoming feature in Grouper 2.4 patch)
Grouper allows you to assign tags (called types) to objects such as folders and groups. There can be metadata on the assignment.
Grouper types helps support and clarify the usage of types as defined in the TIER Grouper Deployment Guide
Attribute definitions
| Definition | Assigned to | Purpose | Value | Cardinality |
|---|---|---|---|---|
| grouperObjectTypeDef | folder, group | identify a group type | marker | Multi assign |
| grouperObjectTypeValueDef | folder assignment, group assignment | name/value pairs | String | Single assign, single valued |
Attribute names
| Name | Definition | Value |
|---|---|---|
| grouperObjectTypeMarker | groupTypeDef | <none> |
| grouperObjectTypeName | groupTypeValueDef | ref, basis, policy,etc, bundle, org, test, service, app. See the TIER Grouper Deployment Guide for descriptions. |
| grouperObjectTypeDataOwner | groupTypeValueDef | e.g. Registrar's office owns this data |
| grouperObjectTypeQueryDescription | groupTypeValueDef | human readable description |
| grouperObjectTypeDirectAssignment | groupTypeValueDef | if this is directly assigned or inherited |
| grouperObjectTypeServiceName | groupTypeValueDef | name of the service that this app falls under |
| grouperObjectTypeOwnerStemId | groupTypeValueDef | if this is not a direct assignment, then this is the stem id where it is inherited from |
Assign type on UI
On a folder or group, a menu item should say "Type." This will only show if user can edit types.
Table should show which are assigned, if inherited or not. There is also the option to add more assignments. If assigned, call the keep inherited method below.
Note: implement the attributes like "Deprovisioning" used attributes
View on UI
Note, if a user can view a group, they can view this attribute assignment from a high level.
On the group or folder screen show what type(s) this group is
Show the data owner and service description if applicable
If there are other lists of objects where there is space, either add it or add it to the tooltip
Screenshots
Just like above, similar Type configuration can be set on groups as well.
Keep inherited attributes up do date
A daemon should work like deprovisioning where inherited attributes are kept up to date. When an attribute is assigned it should call the propagate method for this object and subobjects if a stem.
To do now
Put type name first, then direct/indirect
When settings changed, it should use logic like deprovisioning where it updates the hierarchy tree
Types and metadata should be displayed on object page under the description (not in "more")
To do later
Source basis and ref metadata from loader
Clarify the difference between app and service
If there is a blank attribute, it should be unassigned
Use this as a means to search for things