Page restriction improvement ---------------------------- Key: JBPORTAL-2080 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2080 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Security Affects Versions: 2.6.6 Final Reporter: Thomas Heute Assignee: Sohil Shah Say you have a portal named A *restricted* to everybody Say that on this portal you have a page B which is the default page, with *read* permission to everybody Accessing: http://localhost:8080/portal/portal/A/B will be granted since B can be read http://localhost:8080/portal/portal/A will not be granted since A cannot be read (even though it would show page B since it's the default page) The behavior is understandable, but a bit weird when used. We should define: - Do we need all parents (recursively) to be readable to read a certain page ? or - Do we just check the final node ? In that case we should still check access to the default page of a portal This could be configurable in config.xml -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira