Bug 1094154

Summary: Make permission defaults in page creation forms consistent
Product: [JBoss] JBoss Enterprise Portal Platform 6 Reporter: Peter Palaga <ppalaga>
Component: PortalAssignee: Peter Palaga <ppalaga>
Status: CLOSED UPSTREAM QA Contact: Marek Baluch <mbaluch>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: epp-bugs, ppalaga
Target Milestone: ER02   
Target Release: 6.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Previously, the permission defaults were not set uniformly in page creation forms such as "Page Creation Wizard", "New Page" in Page Management or "Create Page" in Navigation Editor. Optimizations to the classes controlling page permissions made the permission defaults in the named forms consistent.
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-02-10 03:35:45 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Peter Palaga 2014-05-05 07:55:48 UTC
Description of problem:
This is a followup of the rejected Bug 1090875 which asked for applying move*Permission defaults from parent site. The present aim is to ensure for all page creation forms, that they use consistent defaults for all kinds of permissions.
The page creation forms for which this applies:
I. Page Creation Wizard accessible via Toolbar > Site Editor > Add New Page 
II. New Page accessible via Toolbar > Group > Administration > Page Management > Add New Page
III. Create Page accessible via Toolbar > Manage Sites > Edit Navigation > Create Node > Page Selector > Create Page
For each of them, the defaults should be set as follows:
(1) For portal pages the access and edit permissions should be taken from the parent site.
(2) For group pages, the the default access permissions should be set to all group members and edit should be set only to the given group's members with the membership type defined in navigation.creator.membership.type configuration parameter of UserACL service.
(3) For any kind of page (portal, group, etc.), the move*Permissions form defaults are taken over form the page.xml template chosen in the given form. If the given form offers no page template choice, the empty template should be used.
In the present implementation, the named requirements are mostly met, however the code is spread over several classes, and is not always 100% consistent, which should hereby be fixed.

Version-Release number of selected component (if applicable):
JBoss Portal 6.2.0.ER1

How reproducible:
Always

Steps to Reproduce:
Open any of the named page creation forms and check the permission defaults preset by the portal. OK if they match the rules named above, unexpected otherwise.

If there is no UI for the permissions in the give page creation from, create a page and subsequently open it in Page Editor, open Page Properties, and check if the stored permissions.

Comment 2 Peter Palaga 2014-05-05 08:20:38 UTC
https://github.com/gatein/gatein-portal/pull/850 was merged in upstream.

Comment 3 Petr Mensik 2014-06-05 13:54:59 UTC
I confirm that permissions are correctly inherited.

Comment 8 Red Hat Bugzilla 2025-02-10 03:35:45 UTC
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.