[JBoss JIRA] Created: (GTNPORTAL-1008) Gadget permissions are not working correctly (gagdet with restricted access in the AppReg are visible)
by Tugdual Grall (JIRA)
Gadget permissions are not working correctly (gagdet with restricted access in the AppReg are visible)
------------------------------------------------------------------------------------------------------
Key: GTNPORTAL-1008
URL: https://jira.jboss.org/jira/browse/GTNPORTAL-1008
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Security
Affects Versions: 3.0.0-GA
Reporter: Tugdual Grall
When in the App registry a gadget as been set to visible only to a restricted audience this permission is not used when in the portlet/gadget catalog.
Use case:
1- Connect as Root
2- Go in the App Registry
3- Select one gadget, for example ToDo
4- Set the permission to /platform/administrators usrs
5- log out
6- connect as mary/gtn
7- go to your dashboard
8- click add gadget:
9 - BUG: you can see the ToDo Gadget and you can add it to the page ( You are not supposed to)
10 - Edit your page
11- Click on Gadget:
12- BUG: you can see the ToDo gadget (same bug as before)
13-BUG Add it on the page, you can drop it but it wil not be visible (protected content) since you are not allowed to do it.
FIX: we need to hide the gadget from the catalog when the permissions are set.
--
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
13 years
[JBoss JIRA] Created: (GTNPORTAL-1610) Cache portal config for the scope of the request
by Marek Posolda (JIRA)
Cache portal config for the scope of the request
------------------------------------------------
Key: GTNPORTAL-1610
URL: https://jira.jboss.org/browse/GTNPORTAL-1610
Project: GateIn Portal
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Performance
Affects Versions: 3.1.0-GA
Environment: EPP 5.1.0 ER3
Reporter: Marek Posolda
Assignee: Julien Viet
I found another thing for logged user case performance, which can be improved. Issue is that method UserPortalConfigService.getUserPortalConfig() is called two times during HTTP request of logged user. And this method is expensive, because it performs other calls to IDM and DataStorage. So it should be possible to call it only once per HTTP request.
Now it's called from:
1. LocalizationLifecycle.onStartRequest()
2. PortalStateManager.restoreUIRootComponent() . After this call is obtained UserPortalConfig saved as attribute into PortalRequestContext.
It should be possible to save it into PortalRequestContext after LocalizationLifecycle.onStartRequest(), so that PortalStateManager.restoreUIRootComponent() can read it from PortalRequestContext. Or create another Lifecycle class for this purpose (Something similar to UserProfileLifecycle, which is doing similar thing for obtain UserProfile) ?
--
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
13 years, 2 months