Page Comparison

...

The uPortal 2.1 group service is a composite service made up of one or more component services. Each group service functions to represent group information in a consistent manner. The default implementation is delivered with a group service that uses the portal database as its source. Therefore, as delivered, the composite group service only has one component service that is called "local" A demo LDAP component service can be configured by uncommeting the ldap section in the property file compositeGroupServices.xml located in the /properties/group directory. This will setup an "ldap" service that uses the Columbia LDAP directory as its source. If you want to use another LDAP directory, you should modify the LDAPGroupStoreConfig.xml file located in the same file directory. It should also be kept in mind that group information from some services may be read-only. For a more detailed discussion of configuration issues, refer to the Groups documentation.

The groups framework represents a network of groups. A group can be a member of zero or more groups. The group members have privileges assigned to them directly or by virtue of their membership in a containing group (i.e. inherited from the hierarchy of group memberships). As such, the framework allows for multi-inheritance. This is important to realize while using the Groups Manager channel because the question soon arises where one starts the representation of the groups system. The uPortal 2.1 group service allows for the definition of special groups called root groups. A root group is a special group that is the parent of all groups of a specific entity type. Although the groups framework does not enforce this relationship, the groups manager channel requires root groups to organize the opening view. Root groups are also used by the search function to discover the entity types that can be searched. In the default implementation, the "All categories" group (see Figure 1) is the root group of all channel definition groups and the "Everyone" group is the root group of all IPerson groups. Root groups are defined in the portal properties file as properties named with the prefix "org.jasig.portal.services.GroupService.key_" followed by an entity type class name. These properties are used by a group service to determine which groups are root groups. The value of the property is the group key. This key takes the form groupServiceName.key in the default implementation. (See Appendix II: Creating New Root Groups for more details)

...

A quick start tutorial of the Groups Manager channel is located in Appendix I: Test Drive section of this document. For a more detailed discussion of Groups, see the Groups documentation.

Navigation of the Views

When the Groups Manager opens, the channel displays all root groups (see Overview above) for which the user has view permissions (see Figure 1). A group can be expanded by clicking on the icon or collapsed by clicking on the icon. User permissions determine the group members that the user sees as well as the functions that are made available for each group member. Some functionality may also be withheld because the group service itself is read-only. If a user does not have permission to view a parent group (e.g. Faculty), but does have permissions for a sub-group (e.g. Tenured Professors), the parent group will not be visible. If the group Tenured Professors is not a member of any other group that is displayed, it will be invisible to the user from the tree view. The only way for the user to see the group is to search for it (See Searching below).

...

After clicking on the Assign Permissions button, you will see the same detail view 1 as displayed for the Add Member View (see Figure 4). You will be granting permissions for the target group that was being edited in the previous view. You can select the group members to which you want to grant permissions by clicking in the checkbox to the left of the group member's name and then clicking on Select Marked (see the See Add Member View discussion for more details). Once you have clicked on the Done with Selection button, the Permissions Manager channel will be displayed. This view shows a grid with the principals that were selected in the previous view as rows and with all of the defined permissions as columns. You can select Grant or Deny permissions from each of the drop lists. The permissions will be saved once you click on the Submit button. For a detailed description of the Permissions Manager, refer to the Permissions Manager documentation.

Figure 5 Permissions Manager View

...

1. Log in as a portal administrator. By default, all users in the Developers group are portal administrators.
2. Click on the Admin Tools tab where the Groups Manager channel is located.
3. Expand the Faculty group in the Groups Manager channel by clicking on the icon that is next to the group name "Faculty".
4. Open the detail view of the Faculty group by clicking on the group name "Faculty" (to the right of the icon).
5. Click on the !showprops.jpg| Image Added next to the Associate Professors group to show the properties for this group.
6. Click on the to hide the properties.
7. Click on the to close the detail view.

...

1. Click on the group name "Faculty" to re-open the detail view.
2. Edit the Faculty group by clicking on the icon.
3. Change "(new group name)" to "Nutty Prof" and click on the Create New Member Group button.
4. Click on the icon to finish editing the group.
5. Click on the Nutty Prof group that is in the detail view.
6. Click on the Image Removed Image Added icon to edit the group.
7. Change the Nutty Prof group to Nutty Professors and add a description the description "Son of Flubber". Click on the Update button to save the changes.

...

1. Click on the Add Members button.
2. Search for a Person that contains demo. Click on Go .
3. Show the properties for the entity "demo" by clicking on the Image Added icon that is next to "demo". You are doing this to make sure you have the right member.
4. Click on the checkbox next to "demo". This visually selects the member.
5. Click on the Select Marked button. This records all of your selections.
6. Click on the checkbox next to "demo" but this time in the Selected Members section at the bottom of the view. You have visually selected the member.
7. Click on the Deselect Marked button. This removes the member from the selection list.
8. Repeat steps 18 and 19.
9. Click on the Done with Selection button. Everyone on the selection list is now made a member of the group Faculty.

...

1. Open the detail view by clicking on the Faculty group in the tree view on the left (you mean I don't have to explicitly unlock the group?).
2. Open the detail view on Nutty Professors by clicking on its group name in the detail view.
3. Lock this group by clicking on the Image Added icon.
4. Delete the Nutty Professors group by clicking on the Image Added icon.
5. Respond "Yes" to the prompt.

There are four icons used for paging functions that only show up if the number of group members exceed the pageSize that is defined in main_html.xsl. The default size is set to 12. These icons are used as follows:

Appendix II: Creating New Root Groups
At present, the Groups Manager channel does not have a function to create root groups for new entity types. In order to manage a new entity type through the Groups Manager channel, you must do the following:

...