Jetspeed 2
  1. Jetspeed 2
  2. JS2-478

admin portlets application inconsistency

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.0-FINAL
    • Fix Version/s: 2.1-dev, 2.1
    • Component/s: Admin Portlets
    • Labels:
      None
    • Environment:
      W2K, VM 5.0, Tomcat 5.5.12, MySQL 4.1

      Description

      A user can add administration portlets with the portlet selector to the personalsed page (psml).
      This added portlets will not work (Portlet is Not Available: j2-admin::JetspeedUserAdmin
      Reason: null).
      There's no point in that.
      The selector portlet have to filter all portlets to display runnable and entitlements portlets only.

        Activity

        Hide
        Ate Douma added a comment -

        Must already have been fixed sometime ago, as this now works as expected, e.g. PortletPermissions for j2-admin are enforced
        so only a user with the admin role will be able to access them.

        Note: I did find an invalid configuration for PostgreSQL in its populate-userinf-for-default-psml.sql script, but I've fixed that now too.

        Show
        Ate Douma added a comment - Must already have been fixed sometime ago, as this now works as expected, e.g. PortletPermissions for j2-admin are enforced so only a user with the admin role will be able to access them. Note: I did find an invalid configuration for PostgreSQL in its populate-userinf-for-default-psml.sql script, but I've fixed that now too.

          People

          • Assignee:
            Unassigned
            Reporter:
            Michael Gustav Simon
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development