You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by "Ate Douma (JIRA)" <je...@portals.apache.org> on 2009/04/07 02:09:12 UTC

[jira] Resolved: (JS2-595) allow end users to customize their user based default pages, but no allow them to add administrative portlets

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

Ate Douma resolved JS2-595.
---------------------------

    Resolution: Cannot Reproduce

This might have been an issue with the 2.0 release, not reproducible however on later released versions.  

> allow end users to customize their user based default pages, but no allow them to add administrative portlets
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: JS2-595
>                 URL: https://issues.apache.org/jira/browse/JS2-595
>             Project: Jetspeed 2
>          Issue Type: Wish
>          Components: Admin Portlets
>    Affects Versions: 2.1
>         Environment: windows 
>            Reporter: Scott Taylor
>
> I would like (and this may be possible and just improperly configured) to allow all of my users to edit their personal default .psml pages.  However, the customizer allows them to select the administrative portlets also (ie PAM, PALM, others you don't want the masses to have access to).  Since this selection aggregates a new .psml page (or alters the existing) the portlets are added from the portlet level, defeating security constraints (since they are not coded at the portlet level, but at the .psml level.  I understand the need for the customizer to see these portlets, although I personally could handle removing them from the selection and forcing hard-coding of the particular portlets due to their capabilities.
> Is there a fix for this, or some way to alter the customizer to only select portlets from certain WAR's (short of rewriting the customizer).  The portlet-selector.vm page has some code, but it appears to be pulling from another component for db access.  Again, I would prefer to not crack into the guts of the admin portlets if possible.

-- 
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