[ http://issues.apache.org/jira/browse/JS2-241?page=all ]
Ate Douma updated JS2-241:
--------------------------
Fix Version/s: (was: 2.1)
Resolution will take too much time to make it for the 2.1 release
> Admin User/Group/Role Portlet enhancements
> ------------------------------------------
>
> Key: JS2-241
> URL: http://issues.apache.org/jira/browse/JS2-241
> Project: Jetspeed 2
> Issue Type: Improvement
> Components: Admin Portlets
> Affects Versions: 2.0-M2, 2.0-M3, 2.1
> Reporter: Ate Douma
> Assigned To: Ate Douma
>
> 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
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
