[JBoss JIRA] Created: (JBPORTAL-1239) page level security not honored in the navigation system
by Stephen Westbom (JIRA)
page level security not honored in the navigation system
--------------------------------------------------------
Key: JBPORTAL-1239
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1239
Project: JBoss Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Portal Security
Affects Versions: 2.6.Alpha2
Environment: Windows XP
Reporter: Stephen Westbom
Assigned To: Julien Viet
In 2.4 sp1 pages are checked for security before being displayed as a tab in the navigation using this jsp:
jboss-portal.sar\portal-core.war\WEB-INF\jsp\catalog\index.jsp
This seems to be handled by the psib request parameter (a map). In 2.4 the map only gives you PortalNodeURLs that you have permissions on, in all the 2.6 versions you get all the siblingURLs (your term in the JSP page) regardless of the permission settings in the {project name}_object.xml
Can this be fixed so that the psib parameter only gives you a handle to a map that gives you objects you have permissions to see?
Thanks
Stephen
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 3 months
[JBoss JIRA] Updated: (JBPORTAL-857) Deal with non standard Locales better
by Julien Viet (JIRA)
[ http://jira.jboss.com/jira/browse/JBPORTAL-857?page=all ]
Julien Viet updated JBPORTAL-857:
---------------------------------
Fix Version/s: 2.6_Chris_Not_Managed_Tasks
(was: 2.6.CR2)
> Deal with non standard Locales better
> -------------------------------------
>
> Key: JBPORTAL-857
> URL: http://jira.jboss.com/jira/browse/JBPORTAL-857
> Project: JBoss Portal
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Portal WSRP
> Affects Versions: 2.4 Final
> Reporter: Chris Laprun
> Assigned To: Chris Laprun
> Priority: Minor
> Fix For: 2.6_Chris_Not_Managed_Tasks
>
> Original Estimate: 3 hours
> Remaining Estimate: 3 hours
>
> Per the WSRP Spec regarding UnsupportedLocale fault:
> The Portlet does not support generating markup for the requested locale. Since the Portlet is not required to generate markup in the requested locale, a Portlet returning this fault message is indicating that it processes locales in a stricter manner and has no markup for the requested locales. The Consumer can treat this as a specialization of the OperationFailed fault message and does not have to retry getting the markup in other locales.
> Currently, LocaleInfo throws an IllegalArgumentException if the locale is not standard which gets wrapped into an OperationFailedFault at the handler level. We should deal with locale errors better and maybe be more lenient as to what we accept.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 3 months