Page History

Use Spring MVC and Web-Flow

Use same underlying technologies as Jasig CAS, thereby reducing skill sets necessary to deploy and customize a CAS-protected grouper installation.

U Montreal

HTML customization

Use CSS themes (perhaps along the lines of csszengarden) and customizable JSP header and footer includes.

U Penn
Cru (CCCI)

Internationalization (i18n)

One language could be globally configured. Supporting multiple language would be better, but it's not a top priority. It could be detected from the browser (which is nice, but a default value would also work) but it has to be user-changeable using a drop-box or link of some kind since browser language might not be what the user prefers to see.

U Montreal
Cru (CCCI)

Display group relationships

Visual display of groups impacting membership of a given group. Would illustrate subgroups and composite factors, perhaps expanded by levels.

U Montreal

UX participation

User eXperience professional can help with process to ensure good UI usability and workflow.

U Chicago

Images of people in person picker

We would like a future Grouper UI to be able to display an image/photo of a subject (person) when choosing subjects to add as members of a group
We would like a future Grouper UI to be able to display an
image/photo of a subject (person) when choosing subjects to
add as members of a group

LIGO

Why isn't subject a member search/display

Would be nice to have a way to search a group's membership and display why a particular subject is not a member of a group.  Example: given group x:y:allowed I'd lookup a subject and the UI would display that the subject is not a member of the group because of membership in x:y:deny or the subject is not a member of any groups which make up :allowed.  This would be very helpful for debugging a particular subject's membership issues when there are a lot of composite groups in play affecting the final group in question.

U Chicago

Roles/Permissions Area (Lite UI)

Roles/Permissions work flow is somewhat complex and counter intuitive. The hierarchy graph and role/permissions display widgets are cool, but data entry flow could be improved. Maybe better documentation would be helpful. Are there any plans for this?

UCLA

Action Timer

Would be great when viewing details of a group to see when changes to a group will next be provisioned to downstream systems (or updated from external source)

U Chicago

Mobile-Aware

As mentioned in the architecture section above as a possibility, an interface optimized for use with mobile devices (smartphones and tablets)

Stanford
Cru (CCCI)

Clone

Astem:AGroup exists including attributes and values, want to clone it to Bstem:BGroup with attribute names changing "namespace" from A to B. Users often want a new group that is "just like this existing group but different".

LIGO

Attribute handling at objects

It would be realy nice to handle attribute usage for groups, memberships and so on the page that handles the object. See the UI being developed at Uppsala University.

Uppsala University
Cru (CCCI)

Sample UI from SURFnet

See the SURFteams UI for an example of  handling invitations to join a team (using federated email addresses), creating and deleting teams, adding and deleting members, managing team roles (member, manager, admin), and requesting access.

Cru (CCCI)

Sample Propotype UI from University of Washington

The team at University of Washington is developing a prototype Groups Service UI. This UI was demonstrated at the Grouper working group session at 2012 SMM in Arlington, VA. It was agreed that this prototype UI has a clean look and is easy to navigate.

Metadata about provisioning

Be able to attach built in attributes to identify on a UI where the group is used, and how long the provisioning takes (maybe range?)

Working group meeting

Encapsulated composites

Would be nice if the UI treated include/exclude lists and require groups differently (maybe if they follow a naming convention) so the user doesnt need to know which grouper is the whitelist etc, the UI makes it easy.  Maybe this is in phase 2...

Chris

SSO to Grouper UI

Here at the University of Hawaii we also use CAS for authentication.  SSO to the Grouper UI would be very beneficial

University of Hawaii (taken from comment below)
Cru (CCCI)

Hide complexity by default

Hide all of the "internal" attributes (such as ID, ID Path, UUID, etc.).  Only show the user-friendly names, paths, and descriptions.  The details will only become visible through a special setting.  The Lite UI does this now, and I think the entire UI should do this going forward.  I'd recommend that each user have a "profile" where they can set this kind of option globally... so that power users can always see the IDs, etc. but "normal" users will never be bothered by them.

Cru (CCCI)

Batch membership update from UI

Be able to assign multiple subjects to a group by entering them all into a text-area in the group page

U Montreal