[JBoss JIRA] (GTNPORTAL-3275) Upgrade CDI Portlet Integration library to 1.0.3.Final
by Ken Finnigan (JIRA)
Ken Finnigan created GTNPORTAL-3275:
---------------------------------------
Summary: Upgrade CDI Portlet Integration library to 1.0.3.Final
Key: GTNPORTAL-3275
URL: https://issues.jboss.org/browse/GTNPORTAL-3275
Project: GateIn Portal
Issue Type: Component Upgrade
Security Level: Public (Everyone can see)
Components: Packaging
Reporter: Ken Finnigan
Assignee: Ken Finnigan
Upgrade to 1.0.3.Final which fixes the problem of rf:fileUpload being broken when CDI is enabled.
By default it no longer wraps multipart requests, but that can be enabled through a portlet filter init-param.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 6 months
[JBoss JIRA] (GTNPORTAL-2899) The membership type "*" is not interpreted
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-2899?page=com.atlassian.jira.pl... ]
Trong Tran updated GTNPORTAL-2899:
----------------------------------
Sprint: Sprint 81, Sprint 82 (was: Sprint 81)
> The membership type "*" is not interpreted
> -------------------------------------------
>
> Key: GTNPORTAL-2899
> URL: https://issues.jboss.org/browse/GTNPORTAL-2899
> Project: GateIn Portal
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Affects Versions: 3.5.3.Final
> Environment: eXo Platform 4.0.0-Beta2
> Reporter: Hela Zekri
> Assignee: Trong Tran
> Priority: Blocker
> Labels: portal-s71, worked
> Fix For: 3.7.0.Final
>
> Original Estimate: 4 hours
> Time Spent: 3 hours
> Remaining Estimate: 0 minutes
>
> {color:red}
> In eXo Platform, we have the membership type "*". If user has this membership type in a group, it means that he has all membership types in this group.
> {color}
> *Please try this scenario :*
> Add a user that has the membership type "manager" in "/platform/administrators" group and the membership type "*" in "/platform/users" group.
> When this user clicks "add page" in "Page Management", he has the possibility to choose the owner type "group" or "portal". If he chooses "group", the expected output is that he gets as "Owner Id", a selectbox that contains all groups in which he has the membership type "manager".
> (!) The membership type "manager" is set in "portal-configuration.xml" as value-param to UserACL component :
> {code:xml}
> <value-param>
> <name>navigation.creator.membership.type</name>
> <description>specific membership type have full permission with group navigation</description>
> <value>manager</value>
> </value-param>
> {code}
> In this case, user should get as "Owner Id" a selectbox that contains "/platform/administrators" and "/platform/users" groups(The membership type "*" includes "manager" membership type).
> But the current behavior is that the selectbox of "Owner Id" contains only the group "/platform/administator". This is due to the fact that the relationship "*" is considered as a String and not interpreted.
> *There are two possible solutions to this problem :*
> 1- Set the possibility to put many values for "navigation.creator.membership.type" value-param. So that we could do for example :
> {code:xml}
> <value-param>
> <name>navigation.creator.membership.type</name>
> <description>specific membership type have full permission with group navigation</description>
> <value>*,manager</value>
> </value-param>
> {code}
> 2- In "_findRoles_" method in "_org.picketlink.idm.impl.api.session.managers.RoleManagerImpl_" class :
> In the code bellow, each relationship of a user is compared to roleType ("manager"). If it is equal, it will be added to the list that will be returned. So even "*" is compared to "manager", it is not equal, so it won't be added.
> {code}
> for (IdentityObjectRelationship relationship : relationships)
> {
> if (roleType != null)
> {
> if (roleType.getName().equals(relationship.getName()))
> {
> roles.add(new SimpleRole(new SimpleRoleType(relationship.getName()), createUser(relationship.getToIdentityObject()), createGroup(relationship.getFromIdentityObject())));
> }
> }
> else
> {
> roles.add(new SimpleRole(new SimpleRoleType(relationship.getName()), createUser(relationship.getToIdentityObject()), createGroup(relationship.getFromIdentityObject())));
> }
> }
> {code}
> We created [https://issues.jboss.org/browse/PLIDM-40] in which we propose a patch that adds a test on "*" value.
> In the patch, we changed :
> {code}
> if (roleType.getName().equals(relationship.getName()))
> {code}
> to :
> {code}
> if ((roleType.getName().equals(relationship.getName())) || relationship.getName().equals("*"))
> {code}
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 6 months
[JBoss JIRA] (GTNPORTAL-3254) Configure Organization Service TCK tests for the PicketLink implementation
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3254?page=com.atlassian.jira.pl... ]
Trong Tran updated GTNPORTAL-3254:
----------------------------------
Sprint: Sprint 77, Sprint 78, Sprint 79, Sprint 81, Sprint 82 (was: Sprint 77, Sprint 78, Sprint 79, Sprint 81)
> Configure Organization Service TCK tests for the PicketLink implementation
> --------------------------------------------------------------------------
>
> Key: GTNPORTAL-3254
> URL: https://issues.jboss.org/browse/GTNPORTAL-3254
> Project: GateIn Portal
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Identity integration
> Reporter: Trong Tran
> Assignee: Tuyen Nguyen The
> Labels: backlogs
> Fix For: 3.7.0.Final
>
> Original Estimate: 1 day
> Time Spent: 1 day, 3 hours, 30 minutes
> Remaining Estimate: 2 hours
>
> Here is the link for org service TCK documentation : http://docs.jboss.org/exojcr/1.15.4-GA/developer/en-US/html_single/#Core....
> Some examples :
> https://github.com/exodev/core/blob/master/exo.core.component.organizatio...
> https://github.com/exodev/core/blob/master/exo.core.component.organizatio...
> https://github.com/exodev/jcr-services/blob/master/pom.xml
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 6 months
[JBoss JIRA] (GTNPORTAL-3245) Add comfriming when user remove permissions on edit page & site
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3245?page=com.atlassian.jira.pl... ]
Trong Tran updated GTNPORTAL-3245:
----------------------------------
Sprint: Sprint 77, Sprint 78, Sprint 79, Sprint 81, Sprint 82 (was: Sprint 77, Sprint 78, Sprint 79, Sprint 81)
> Add comfriming when user remove permissions on edit page & site
> ---------------------------------------------------------------
>
> Key: GTNPORTAL-3245
> URL: https://issues.jboss.org/browse/GTNPORTAL-3245
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 3.6.1.Final
> Reporter: Hai Nguyen
> Assignee: Hai Nguyen
> Priority: Minor
> Labels: backlogs
> Original Estimate: 4 hours
> Time Spent: 2 days, 3 hours
> Remaining Estimate: 0 minutes
>
> - Login portal
> - Go to user and group management
> - Choose Group management tab
> - Add new group ( ex: AAA)
> - Go to Pages
> - Add new page for group above
> - Search this page and click edit
> - Click view page properties
> - Change access and edit permission to ( organization/*)
> - Click Finish button on Editor composer
> => Unknown error and throw exception in console
> {noformat}
> 2013-08-08 15:20:18,549 | ERROR | Error during the processAction phase [portal:UIPortalApplication<http-nio-0.0.0.0-8080-exec-10>]
> java.lang.NullPointerException: null
> at org.exoplatform.portal.webui.portal.UIPortalComposer$FinishPageEditionActionListener.execute(UIPortalComposer.java:680) ~[exo.portal.webui.portal-3.5.6-PLF.jar:3.5.6-PLF]
>
> {noformat}
>
> Reproduce on edit site is the same
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 6 months
[JBoss JIRA] (GTNPORTAL-3263) "Restricted" page editor
by Peter Palaga (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3263?page=com.atlassian.jira.pl... ]
Peter Palaga updated GTNPORTAL-3263:
------------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> "Restricted" page editor
> ------------------------
>
> Key: GTNPORTAL-3263
> URL: https://issues.jboss.org/browse/GTNPORTAL-3263
> Project: GateIn Portal
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Peter Palaga
> Assignee: Peter Palaga
> Fix For: 3.7.0.Final
>
>
> See https://community.jboss.org/wiki/RestrictedPageEditor
> A customer is willing to give the ability to many different users to edit pages. Those users would require a simplified page editor and be constrained to simple actions. In particular, users should not be able to compose complex pages and risk to break the layouts.
> The layouts should be restricted to what is available from the "Containers" tab of the editor.
> In particular the 2 following scenarios should not be possible:
> Scenario 1: User should not be able to put an application above/below the 2 column layout (As this break the pre-defined layouts, suddenly the user is able to have a single column representation while this may not have been provided):
> Scenario 2: User should not be able to put a layout within a layout (only above or below existing ones)
> Proposed solution
> Add an option in configuration.properties for a restricted page and layout editor. This would apply across the whole portal.
> gatein.portal.pageeditor.mode=full (default) | restricted
> gatein.portal.layouteditor.mode=full (default) | restricted
>
> Applications could only be added to predefined layouts (and not directly on a page).
> Containers could only be added to the root of a page (not inside another container).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 6 months
[JBoss JIRA] (GTNPORTAL-3263) "Restricted" page editor
by Peter Palaga (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3263?page=com.atlassian.jira.pl... ]
Peter Palaga updated GTNPORTAL-3263:
------------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/gatein/gatein-portal/pull/677
> "Restricted" page editor
> ------------------------
>
> Key: GTNPORTAL-3263
> URL: https://issues.jboss.org/browse/GTNPORTAL-3263
> Project: GateIn Portal
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Peter Palaga
> Assignee: Peter Palaga
> Fix For: 3.7.0.Final
>
>
> See https://community.jboss.org/wiki/RestrictedPageEditor
> A customer is willing to give the ability to many different users to edit pages. Those users would require a simplified page editor and be constrained to simple actions. In particular, users should not be able to compose complex pages and risk to break the layouts.
> The layouts should be restricted to what is available from the "Containers" tab of the editor.
> In particular the 2 following scenarios should not be possible:
> Scenario 1: User should not be able to put an application above/below the 2 column layout (As this break the pre-defined layouts, suddenly the user is able to have a single column representation while this may not have been provided):
> Scenario 2: User should not be able to put a layout within a layout (only above or below existing ones)
> Proposed solution
> Add an option in configuration.properties for a restricted page and layout editor. This would apply across the whole portal.
> gatein.portal.pageeditor.mode=full (default) | restricted
> gatein.portal.layouteditor.mode=full (default) | restricted
>
> Applications could only be added to predefined layouts (and not directly on a page).
> Containers could only be added to the root of a page (not inside another container).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 6 months
[JBoss JIRA] (GTNPORTAL-2899) The membership type "*" is not interpreted
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-2899?page=com.atlassian.jira.pl... ]
Trong Tran reopened GTNPORTAL-2899:
-----------------------------------
The latest kernel depends on cdi 1.1 which is in conflict with the version of cdi embedded in JBoss AS 7.
So we would wait for a downgrade to CDI 1.0 in Kernel https://jira.exoplatform.org/browse/KER-269
> The membership type "*" is not interpreted
> -------------------------------------------
>
> Key: GTNPORTAL-2899
> URL: https://issues.jboss.org/browse/GTNPORTAL-2899
> Project: GateIn Portal
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Affects Versions: 3.5.3.Final
> Environment: eXo Platform 4.0.0-Beta2
> Reporter: Hela Zekri
> Assignee: Trong Tran
> Priority: Blocker
> Labels: portal-s71, worked
> Fix For: 3.7.0.Final
>
> Original Estimate: 4 hours
> Time Spent: 3 hours
> Remaining Estimate: 0 minutes
>
> {color:red}
> In eXo Platform, we have the membership type "*". If user has this membership type in a group, it means that he has all membership types in this group.
> {color}
> *Please try this scenario :*
> Add a user that has the membership type "manager" in "/platform/administrators" group and the membership type "*" in "/platform/users" group.
> When this user clicks "add page" in "Page Management", he has the possibility to choose the owner type "group" or "portal". If he chooses "group", the expected output is that he gets as "Owner Id", a selectbox that contains all groups in which he has the membership type "manager".
> (!) The membership type "manager" is set in "portal-configuration.xml" as value-param to UserACL component :
> {code:xml}
> <value-param>
> <name>navigation.creator.membership.type</name>
> <description>specific membership type have full permission with group navigation</description>
> <value>manager</value>
> </value-param>
> {code}
> In this case, user should get as "Owner Id" a selectbox that contains "/platform/administrators" and "/platform/users" groups(The membership type "*" includes "manager" membership type).
> But the current behavior is that the selectbox of "Owner Id" contains only the group "/platform/administator". This is due to the fact that the relationship "*" is considered as a String and not interpreted.
> *There are two possible solutions to this problem :*
> 1- Set the possibility to put many values for "navigation.creator.membership.type" value-param. So that we could do for example :
> {code:xml}
> <value-param>
> <name>navigation.creator.membership.type</name>
> <description>specific membership type have full permission with group navigation</description>
> <value>*,manager</value>
> </value-param>
> {code}
> 2- In "_findRoles_" method in "_org.picketlink.idm.impl.api.session.managers.RoleManagerImpl_" class :
> In the code bellow, each relationship of a user is compared to roleType ("manager"). If it is equal, it will be added to the list that will be returned. So even "*" is compared to "manager", it is not equal, so it won't be added.
> {code}
> for (IdentityObjectRelationship relationship : relationships)
> {
> if (roleType != null)
> {
> if (roleType.getName().equals(relationship.getName()))
> {
> roles.add(new SimpleRole(new SimpleRoleType(relationship.getName()), createUser(relationship.getToIdentityObject()), createGroup(relationship.getFromIdentityObject())));
> }
> }
> else
> {
> roles.add(new SimpleRole(new SimpleRoleType(relationship.getName()), createUser(relationship.getToIdentityObject()), createGroup(relationship.getFromIdentityObject())));
> }
> }
> {code}
> We created [https://issues.jboss.org/browse/PLIDM-40] in which we propose a patch that adds a test on "*" value.
> In the patch, we changed :
> {code}
> if (roleType.getName().equals(relationship.getName()))
> {code}
> to :
> {code}
> if ((roleType.getName().equals(relationship.getName())) || relationship.getName().equals("*"))
> {code}
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 6 months