[JBoss JIRA] Created: (GTNPORTAL-853) Replication of portlet window states is not working
by Marek Posolda (JIRA)
Replication of portlet window states is not working
---------------------------------------------------
Key: GTNPORTAL-853
URL: https://jira.jboss.org/jira/browse/GTNPORTAL-853
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Environment: GateIn trunk (revision 2078) deployed on EAP 5.0 - AS configuration "production",
Sun JDK 1.6
Reporter: Marek Posolda
Fix For: 3.0.0-GA
I have 2 nodes with GateIn portal and one Apache loadbalancer with mod_jk and sticky session enabled.
1) Login as root in loadbalancer
2) Go to page with some portlet and minimize (or maximize) this portlet. For example portlet on newStaff page can be used for this.
3) Kill the GateIn node which serves the session
4) Send another request to newStaff page via loadbalancer. Now request is served on backup node. And I am seeing portlet in normal state (should be minimized) which doesn't seem correct.
--
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
11 years, 10 months
[JBoss JIRA] Created: (GTNPORTAL-882) Smart handling of unconfigured MailService
by Patrice Lamarque (JIRA)
Smart handling of unconfigured MailService
------------------------------------------
Key: GTNPORTAL-882
URL: https://jira.jboss.org/jira/browse/GTNPORTAL-882
Project: GateIn Portal
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Patrice Lamarque
Priority: Optional
An implementation of org.exoplatform.services.mail.MailService that would be able to detect when no configuration is set.
Then it would send an applicative exception that can be catched by the application layer to invite administrators to configure the mailservice with their own.
For instance, it could warn the user : "We could not send the recovery email because your admin has not configured it properly"
And give more directions in the logs for the admin : "The MailService was not configured. Please edit mail-configuration.xml and set your own settings."
--
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
11 years, 10 months
[JBoss JIRA] Created: (GTNPORTAL-1122) Portlet icons locations need to be skin independent [or dependent]
by Matt Wringe (JIRA)
Portlet icons locations need to be skin independent [or dependent]
------------------------------------------------------------------
Key: GTNPORTAL-1122
URL: https://jira.jboss.org/jira/browse/GTNPORTAL-1122
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Matt Wringe
If a portlet wants to have a custom icon shown in the application registry or in the page editor, then they can place a png in a special location.
Currently this location is:
skin/DefaultSkin/portletIcons/PortletName.png
But this icon is shown for all skins, regardless if its the DefaultSkin or not (see ApplicationRegistryServiceImpl.getApplicationIconURL for where its hardcoded to this)
This location should be changed to a location which doesn't mention DefaultSkin, or it should be changed so that it is dependent on the current portal skin (for example skin/SimpleSkin/portleticons/PortletName.png would be the icon if the current portal skin is the SimpleSkin).
--
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
11 years, 10 months
[JBoss JIRA] Created: (GTNPORTAL-1230) Inherited node ACL
by Thomas Heute (JIRA)
Inherited node ACL
------------------
Key: GTNPORTAL-1230
URL: https://jira.jboss.org/browse/GTNPORTAL-1230
Project: GateIn Portal
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Security
Reporter: Thomas Heute
Fix For: 3.2.0-GA
As of now it is difficult to maintain gazillion of nodes even in a hierarchy.
when you have:
A<-B<-C
(B is a child of A, C is a child of B)
and you want to restrict access to that tree, you need to define security rules on the 3 *pages*. (and modify the pages everytime you want to change a restriction)
As of now we don't have security restrictions on the node itself, we would need to add this feature and make it inherited.
the Picketlink Authz framework can do this effectively, but we would need an answer to this issue prior to the integration.
We should be able to tell that A is restricted to admins, and on an access to C check for parent restrictions. It should also be possible to add a restriction on B.
In some cases, one node may want to break the inheritance to define other rules.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 10 months