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 "Randy Watler (JIRA)" <je...@jakarta.apache.org> on 2005/04/21 20:27:30 UTC
[jira] Created: (JS2-236) PageManager Folder/Page security needs to support multiple page.security files
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-M3
Reporter: Randy Watler
Assigned to: Randy Watler
Priority: Minor
Fix For: 2.0-M3
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: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
[jira] Updated: (JS2-236) PageManager Folder/Page security needs to
support multiple page.security files
Posted by "Ate Douma (JIRA)" <je...@portals.apache.org>.
[ https://issues.apache.org/jira/browse/JS2-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ate Douma updated JS2-236:
--------------------------
Fix Version/s: (was: 2.1)
2.2-dev
Rescheduled to post 2.1 release
> PageManager Folder/Page security needs to support multiple page.security files
> ------------------------------------------------------------------------------
>
> Key: JS2-236
> URL: https://issues.apache.org/jira/browse/JS2-236
> Project: Jetspeed 2
> Issue Type: Improvement
> Components: PSML
> Affects Versions: 2.0-M4, 2.0-FINAL
> Reporter: Randy Watler
> Assigned To: Randy Watler
> Priority: Minor
> Fix For: 2.2-dev
>
>
> 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.
-
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
[jira] Updated: (JS2-236) PageManager Folder/Page security needs to support multiple page.security files
Posted by "Randy Watler (JIRA)" <je...@portals.apache.org>.
[ http://issues.apache.org/jira/browse/JS2-236?page=all ]
Randy Watler updated JS2-236:
-----------------------------
Fix Version: 2.0-POST
(was: 2.0-FINAL)
Version: 2.0-M4
2.0-FINAL
(was: 2.0-POST)
> 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-M4, 2.0-FINAL
> Reporter: Randy Watler
> Assignee: Randy Watler
> Priority: Minor
> Fix For: 2.0-POST
>
> 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: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[jira] Assigned: (JS2-236) PageManager Folder/Page security needs
to support multiple page.security files
Posted by "Ate Douma (JIRA)" <je...@portals.apache.org>.
[ https://issues.apache.org/jira/browse/JS2-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ate Douma reassigned JS2-236:
-----------------------------
Assignee: (was: Randy Watler)
> PageManager Folder/Page security needs to support multiple page.security files
> ------------------------------------------------------------------------------
>
> Key: JS2-236
> URL: https://issues.apache.org/jira/browse/JS2-236
> Project: Jetspeed 2
> Issue Type: Improvement
> Components: PSML
> Affects Versions: 2.0-M4, 2.0-FINAL
> Reporter: Randy Watler
> Priority: Minor
> Fix For: 2.2-dev
>
>
> 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.
-
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
[jira] Updated: (JS2-236) PageManager Folder/Page security needs to support multiple page.security files
Posted by "Randy Watler (JIRA)" <je...@portals.apache.org>.
[ 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: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[jira] Updated: (JS2-236) PageManager Folder/Page security needs to support multiple page.security files
Posted by "Michael Lipp (JIRA)" <je...@portals.apache.org>.
[ http://issues.apache.org/jira/browse/JS2-236?page=all ]
Michael Lipp updated JS2-236:
-----------------------------
Fix Version: 2.0-FINAL
(was: 2.0-M4)
> 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-M3
> 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: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[jira] Updated: (JS2-236) PageManager Folder/Page security needs to support multiple page.security files
Posted by "Randy Watler (JIRA)" <je...@portals.apache.org>.
[ http://issues.apache.org/jira/browse/JS2-236?page=all ]
Randy Watler updated JS2-236:
-----------------------------
Fix Version: 2.0-M4
(was: 2.0-M3)
> 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-M3
> Reporter: Randy Watler
> Assignee: Randy Watler
> Priority: Minor
> Fix For: 2.0-M4
>
> 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: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org