Bug 1045509 - It is possible to create new repository named "system"
Summary: It is possible to create new repository named "system"
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: CR1
: 6.0.0
Assignee: Alexandre Porcelli
QA Contact: Jiri Locker
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-20 15:33 UTC by Jiri Locker
Modified: 2014-08-06 20:18 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-06 20:18:31 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Jiri Locker 2013-12-20 15:33:59 UTC 
Description of problem:
I can successfully create "new" repository named "system" in Workbench Administration perspective. This makes the "hidden" system.git repository available in the UI and has dangerous side effects. For example it starts an infinite loop generating new Inbox entries (each inbox modification generates a modification event, which modifies the inbox file and so on...). This pollutes server log and consumes CPU power.

Version-Release number of selected component (if applicable):
ER6

How reproducible:
-

Steps to Reproduce:
1. go to Administration perspective
2. create new repository named "system"

Actual results:
Action is successful. The described side effects.

Expected results:
This action should be prevented.

Additional info:
Comment 1 Alexandre Porcelli 2014-01-03 02:29:01 UTC 
Fix pushed to master and product branch of uberfire repository:

(master) https://github.com/droolsjbpm/uberfire/commit/197dbff64
(0.3.x) https://github.com/droolsjbpm/uberfire/commit/c47827507
Comment 2 Jiri Locker 2014-01-22 12:14:10 UTC 
Fixed in CR1. Attempt to create new repository that already exists now fails and user is informed by an error dialog.
Note You need to log in before you can comment on or make changes to this bug.