Back to bug 1029005

Who When What Removed Added
Martin Weiler 2013-11-11 13:18:34 UTC Link ID JBoss Issue Tracker GTNPORTAL-3287
Jiri Pallich 2013-11-12 14:13:18 UTC CC jpallich
Boleslaw Dawidowicz 2013-11-13 10:10:55 UTC Status NEW ASSIGNED
CC bdawidow
Assignee jbpapp-maint ppalaga
Peter Palaga 2013-11-14 21:00:09 UTC Status ASSIGNED MODIFIED
Boleslaw Dawidowicz 2013-11-26 10:35:00 UTC Status MODIFIED ON_QA
Target Milestone --- DR01
Tomas Kyjovsky 2014-01-08 16:36:33 UTC Status ON_QA VERIFIED
CC tkyjovsk
Boleslaw Dawidowicz 2014-02-07 10:38:37 UTC Doc Text Cause: Buggy code

Consequence: When setting many portal permissions like ":/platform/administrators/admin group1;:/platform/administrators/admin group2;*:/platform/administrators/admin group3" only first one is used.

Fix: Code

Result: Setting many permissions work as expected.
Aakanksha 2014-02-11 11:52:22 UTC CC aasingh
Doc Text Cause: Buggy code

Consequence: When setting many portal permissions like ":/platform/administrators/admin group1;:/platform/administrators/admin group2;*:/platform/administrators/admin group3" only first one is used.

Fix: Code

Result: Setting many permissions work as expected.
The admin has access permissions set as ":/platform/administrators/admin group1;:/platform/administrators/admin group2;*:/platform/administrators/admin group3". It is noticed that "admin group1" is used and "admin group2" and "admin group3" are not used.
The permission is managed by the method "hasPermission".
For example, if the user has the Membership Type "member " set in the group "/platform/administrators/admin group1". While checking the group permissions in a portlet, the value returned is false whereas if the access permission for the admin are set to a single entry , "admin group1", the hasPermission method returns true.
To resolve the problem the method "hasPermission" is changed to accpet a list of Memberships in the Permission parameter.
Aakanksha 2014-02-13 18:04:40 UTC Doc Text The admin has access permissions set as ":/platform/administrators/admin group1;:/platform/administrators/admin group2;*:/platform/administrators/admin group3". It is noticed that "admin group1" is used and "admin group2" and "admin group3" are not used.
The permission is managed by the method "hasPermission".
For example, if the user has the Membership Type "member " set in the group "/platform/administrators/admin group1". While checking the group permissions in a portlet, the value returned is false whereas if the access permission for the admin are set to a single entry , "admin group1", the hasPermission method returns true.
To resolve the problem the method "hasPermission" is changed to accpet a list of Memberships in the Permission parameter.
The admin has access permissions set as ":/platform/administrators/admin group1;:/platform/administrators/admin group2;*:/platform/administrators/admin group3". It was noticed that "admin group1" was used and "admin group2" and "admin group3" were not used. This causes the value of group permissions in a portlet to return false whereas if the access permission for the admin are set to a single entry , "admin group1", the hasPermission method returns true. The fix changes the "hasPermission" method to accept a list of Memberships.
Aakanksha 2014-02-14 06:33:24 UTC Doc Text The admin has access permissions set as ":/platform/administrators/admin group1;:/platform/administrators/admin group2;*:/platform/administrators/admin group3". It was noticed that "admin group1" was used and "admin group2" and "admin group3" were not used. This causes the value of group permissions in a portlet to return false whereas if the access permission for the admin are set to a single entry , "admin group1", the hasPermission method returns true. The fix changes the "hasPermission" method to accept a list of Memberships. It was discovered that when multiple group access permissions were defined, the "hasPermission" method was honoring the first group access permission only. This caused the value of group permissions in a portlet to return false. If an administrator had access permissions set to a single group access permission, "hasPermission" functioned as expected. The fix changes the "hasPermission" method to accept a list of Memberships. For example, if the admin has access permissions set as ":/platform/administrators/admin group1;:/platform/administrators/admin group2;*:/platform/administrators/admin group3", all three access permissions are now accepted.
PnT Account Manager 2018-10-17 21:31:28 UTC CC aasingh
PnT Account Manager 2019-01-01 03:40:35 UTC QA Contact dpospisi tkyjovsk

Back to bug 1029005