Status

An implementation of this specification is ready. (Post GateIn 3.6)

Description

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 two new attributes to Pages and Containers:

• move-apps-permissions
• move-containers-permissions
  

They both would contain the same kind of roles/groups list like the existing access-permissions.

To play well with portals migrated from older GateIn versions and so that the default GateIn behavior would stay the same like it was in previous versions, both move-*-permissions would default to Everybody if they are not set explicitly.

To achieve the behavior requested by the customer, one can create a portal extension (like this one) and override the GateIn defaults therein. E.g. for the "Two Columns" layout the customer would have to customize the its two-columns/page.xml file like this:

<page
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.gatein.org/xml/ns/gatein_objects_1_6 http://www.gatein.org/xml/ns/gatein_objects_1_6"
    xmlns="http://www.gatein.org/xml/ns/gatein_objects_1_6">
  <name></name>
  <add-application-permissions>Nobody</add-application-permissions>
  <container template="system:/groovy/portal/webui/container/UITableColumnContainer.gtmpl">
    <access-permissions>Everyone</access-permissions>
    <add-application-permissions>Nobody</add-application-permissions>
    <add-container-permissions>Nobody</add-container-permissions>
    <container template="system:/groovy/portal/webui/container/UIContainer.gtmpl">
      <access-permissions>Everyone</access-permissions>
      <add-container-permissions>Nobody</add-container-permissions>
    </container>
    <container template="system:/groovy/portal/webui/container/UIContainer.gtmpl">
      <access-permissions>Everyone</access-permissions>
      <add-container-permissions>Nobody</add-container-permissions>
    </container>
  </container>
</page>

Note that <move-*-permissions>Nobody</move-*-permissions> is a shorthand for <move-*-permissions /> - i.e. for an empty list of permissions. In this way, all users (excluding root) are forbidden to place the given kind of component (container or portlet) on the given position in the hierarchy.

Permission Setting UI

This specification adds the ability to set Move-*-Permission of permissions at different location of the UI. They all user the same UI for which we define the specification below

Site Permissions

Page Permissions

Container Permissions