[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1009) optionally login-require in a more specific page should be able to override a wildcard login-require

optionally login-require in a more specific page should be able to override a wildcard login-require ---------------------------------------------------------------------------------------------------- Key: JBSEAM-1009 URL: http://jira.jboss.com/jira/browse/JBSEAM-1009 Project: JBoss Seam Issue Type: Patch Components: Security Affects Versions: 1.2.0.GA Environment: all Reporter: Leo Baschy Assigned To: Shane Bryzak Attachments: may-override-login-required.patch, may-override-login-required.patch, weaker-explicit-security.patch, weaker-explicit-security.patch This should be optional to switch on, so no one's existing expectations of security get broken. The point is about having a generic wildcard <page view-id="*" scheme="http" login-required="true"> to secure the whole site, and then allowing specific pages or specific wildcards to have login-required="false". E.g. for a registration (with preview) section as one cannot be logged in if one isn't registered yet. Some may suggest instead forcing pages into dedicated secure and not-secure directories, but in reality if there are multiple reasons to force pages into directories different ways (security, hyperlink management, publishability of URLs, etc.), one cannot serve all of them.