I see that it is possible to put security constraints in psml files at page level. Is it possible to restrict usage ofNot quite yet, scheduled for 2.0 final release
some exact portlet on page by security constraints so that it is not rendered if user is not in some spesific
group/role.
What we do have is the PortletPermission class, and we can check against it using the JAAS security, however the checks are not being made in the current aggregator.
INSERT INTO SECURITY_PERMISSION VALUES(11,'org.apache.jetspeed.security.PortletPermission','MyPortet','view'...
-- David Sean Taylor Bluesunrise Software [EMAIL PROTECTED] [office] +01 707 773-4646 [mobile] +01 707 529 9194
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]