[ http://issues.apache.org/jira/browse/JS2-236?page=all ]

Randy Watler updated JS2-236:
-----------------------------

    Description: 
PageManager Page/Folder constraints security implementation, (bronco), does not 
support multiple page.security files as documented. At a minimum, subsites need 
to support their own page.security files. Generalizing the implementation to 
support page.security definitions embedded within the site hierarchy should be 
considered... probably with a strict replacement aggregation policy within the 
hierarchy to limit performance overhead.

The current implementation restricts the location of the page.security file to 
the site root folder.


  was:
PageManager Page/Folder constraints security implementation, (bronco), does not 
support multiple page.security files as documented. At a minimum, subsites need 
to support their own page.security files. Generalizing the implementation to 
support page.security definitions embedded within the site hierarchy should be 
considered... probably with a strict replacement aggregation policy within the 
hierarchy to limit performance overhead.

The current implementation restricts the location of the page.security file to 
the site root folder.


        Version: 2.0-POST
                     (was: 2.0-M3)
    Environment: 

> PageManager Folder/Page security needs to support multiple page.security files
> ------------------------------------------------------------------------------
>
>          Key: JS2-236
>          URL: http://issues.apache.org/jira/browse/JS2-236
>      Project: Jetspeed 2
>         Type: Improvement
>   Components: PSML
>     Versions: 2.0-POST
>     Reporter: Randy Watler
>     Assignee: Randy Watler
>     Priority: Minor
>      Fix For: 2.0-FINAL

>
> PageManager Page/Folder constraints security implementation, (bronco), does 
> not support multiple page.security files as documented. At a minimum, 
> subsites need to support their own page.security files. Generalizing the 
> implementation to support page.security definitions embedded within the site 
> hierarchy should be considered... probably with a strict replacement 
> aggregation policy within the hierarchy to limit performance overhead.
> The current implementation restricts the location of the page.security file 
> to the site root folder.

-- 
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to