portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Woonsan Ko (JIRA)" <jetspeed-...@portals.apache.org>
Subject [jira] Resolved: (JS2-1135) Space management security access should be configurable.
Date Fri, 19 Mar 2010 19:44:27 GMT

     [ https://issues.apache.org/jira/browse/JS2-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Woonsan Ko resolved JS2-1135.

    Resolution: Fixed

The following preference is added into three portlets: j2-admin::SpacesManager, j2-admin::SpaceNavigator
and j2-admin::PageNavigator.

      <!-- If the following pref is blank, then the default admin role and admin user is
used. -->
        <value>devmgr, executive</value>

As commented, if the above preference is blank, then the admin role and the admin user name
are used to check if the user is a space admin user. (This is the default option.)
If the preference is set by comma or whitespace separators, then the configured roles are
to be checked as well as the admin role and admin user.

> Space management security access should be configurable.
> --------------------------------------------------------
>                 Key: JS2-1135
>                 URL: https://issues.apache.org/jira/browse/JS2-1135
>             Project: Jetspeed 2
>          Issue Type: Improvement
>          Components: Admin Portlets
>            Reporter: Woonsan Ko
>            Assignee: Woonsan Ko
>            Priority: Minor
>             Fix For: 2.2.1
> Currently, a space can be added by admin role only and can be edited by admin role or
the space owner only.
> The roles need to be configurable (e.g. comma-separated preference values)

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org

View raw message