Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 956130

Summary: User with "Create workspaces" permission can't see the workspaces he created.
Product: [Retired] JBoss BPMS Platform 6 Reporter: Jan Hrcek <jhrcek>
Component: BAMAssignee: David Gutierrez <dgutierr>
Status: CLOSED CURRENTRELEASE QA Contact: Jan Hrcek <jhrcek>
Severity: medium Docs Contact:
Priority: high    
Version: 6.0.0CC: rrajasek, rzhang
Target Milestone: DR4   
Target Release: 6.0.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: Lack of permissions for the user/role who creates a brand new workspace. Consequence: The user can't get access to the workspace just after creating it. Fix: Auto-assign permissions the the creator user within the create workspace operation. Result: The user can access/admin the workspace he creates.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2014-08-06 20:10:00 UTC Type: Feature Request
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jan Hrcek 2013-04-24 10:29:13 UTC 
Description of problem:
User with "Create workspaces" permission can't see/use/edit the workspaces he created. Because when the workspace is created it has initially no permissions assigned (it is visible only to root user, who bypases all the application level permission checking).

Version-Release number of selected component (if applicable):
6.0.0.DR3

How reproducible:
Always.

Steps to Reproduce:
1. Login with root and assign "Create workspaces" permission to Administrator role.
	-In the black management bar at the top click "General congifuration"
	-Expand section "General permissions"
	-In "Permission assignation" table set "Create workspace" permission for Administrator role to Yes, the other permissions 3 to No, click Save
2. Logout root and log back in with some user with Administrator role (e.g. admin)
3. In the black management bar at the top click picture with label "Create workspace", that takes you to page with "Workspaces" panel.
4. Fill in name and title (e.g. MyNewWorkspace for both) and click "Create workspace" button.



Actual results:
The message "The workspace has been successfully created" appears. However, the newly created workspace is not visible to the admin user, so he can't do anything to configure the newly created workspace!

- With admin user, the newly created workspace is nowhere to be seen (in "Workspaces" tree in General configuration, nor on the home page of the dashboard-builder in the "Workspaces" select)
- When you login with root user, the workspace "MyNewWorkspace" created by admin user is visible and working.

The problem is in the initial privileges assigned to workspace - go to "General configuration" page > Workspaces > MyNewWorkspace > Permission you can see, that workspace is created with no permissions assigned to any role.



Expected results:
The workspace should be visible at least to the user, who has permission to create it. The initial privileges of a newly created workspace should be set at least to "Access" and "Administrate" granted to the role, that created it.
Otherwise what is the use of "Create workspaces" privilege, when the workspaces cannot be worked with (except for root user, who is not restricted by any permissions)?


Additional info:
Comment 1 David Gutierrez 2013-05-07 10:57:35 UTC 
Fixed as suggested.

Now the application assigns some default workspace permissions to the creator role so that, just after creating the workspace, the creator user can get access to it.

Github commit: https://github.com/droolsjbpm/dashboard-builder/commit/da149ca0e6ffaabc54c9e7ef119ed6ed624bb4c2
Comment 2 Jan Hrcek 2013-06-11 11:01:09 UTC 
QA: Ok, now it works. Now when user with "Create workspaces" creates a workspace, the workspace is visible to him, as it should be. Verified with dashbuilder DR5 deployed on EAP 6.1.