portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Taylor (JIRA)" <jetspeed-...@portals.apache.org>
Subject [jira] Commented: (JS2-595) allow end users to customize their user based default pages, but no allow them to add administrative portlets
Date Mon, 09 Oct 2006 12:29:20 GMT
    [ http://issues.apache.org/jira/browse/JS2-595?page=comments#action_12440875 ] 
            
Scott Taylor commented on JS2-595:
----------------------------------

I have found a work around for now, but it's not pretty...

I can comment out all of the references to the admin portlets in the js-admin portlet.xml
files, and the set all of the admin .psml pages to hidden, the portal will still work, end
users can still customize their own default.psml pages, and cannot access the administrative
portlets.

Ugly, but it works.

> allow end users to customize their user based default pages, but no allow them to add
administrative portlets
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: JS2-595
>                 URL: http://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.
-
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: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org


Mime
View raw message