[JS2-241] Admin User/Group/Role Portlet enhancements

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.1-dev, 2.1
• Component/s: Admin Portlets
• Assignee: Unassigned
• Reporter: Ate Douma
• Created: 26/Apr/05 21:23
• Updated: 11/May/11 20:16

Description

To be able to use the Admin User/Group/Role portlets for a medium to large (> 10.000) number of users, together with strong security requirements, the following enhancements are envisioned:

Configuration of User Details Portlet contents and behavior:

• allow form based entry of a configurable set of User Attributes
  on a new User Details Portlet tab (User tab)
• specify which tabs are visible (e.g. hide Attributes tab)
• specify default values for role and profile rule for new users (including none)
• specify if default role and/or profile fields should be shown on "Add User" form
• optional display Password tab contents on (new) User tab, allowing Password tab to
  be hidden

Further enhancements to the User Attributes entry Form:

• order and position of each field (row, column)
• i18n labels
• field type: text, boolean (checkbox), list, data (calendar)
• field validation: max length, range, date checks, required (update to null)

Implement enabled property of Principals (User, Role and Group):

• see JS2-151, task 9)

Filter/query enhancements to the User Browser (and User Chooser for Role and Group assignments):

• filter on User Attributes
• filter on PasswordCredential enabled property
• filter for role/group assignment poplists (possibly with client side javascript)
• Preferences based configuration for:
• filter options (which User Attributes can be used in filtering)
• display resultset options (which User Attributes are shown)

Filter/query and resultset enhancements for the User/Group/Role Browsers and Choosers:

• (optionally) do not auto query
• filter on enabled property (see above)
• resultset page navigator controls (<<, <, >, >>)
• Preferences based configuration for:
• table window size (number of records displayed)
• max number of records retrieved
  (retrieving more than say 100 records isn't useful and very memory and time consuming)

Role security restrictions for certain operations:

• differentiate between create/remove/update and assignment tasks
  In some organizations, assignments can be handled by non-administration personnel

Issue Links

• is blocked by: JS2-963 Developer Browser 'Filter by Role' feature needs to be re-implemented in Wicket User Browser portlet
• is blocked by: JS2-964 Enhance the Administrative APIs to be able to scroll over large data sets

Sub-Tasks

• Further enhancements to the User Attributes Entry Form: Open
• Filter/query enhancements to the User Browser and User Chooser for Role and Group assignments: Open
• Filter/query and resultset enhancements for the User/Group/Role Browsers and Choosers: Open
• Role security restrictions for certain Admin Portlet operations: Open