Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0004293Openbravo ERPJ. Demo datapublic2008-07-03 09:472011-03-03 23:33
Reporterroklenardic 
Assigned Tormorley 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionno change required 
PlatformOS20OS VersionUbuntu 8.04
Product Version 
Target VersionFixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customer
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0004293: Separate user for System Administrator
DescriptionCurrently, our demo data has one main user, Openbravo with the password of openbravo. This then has access to all roles, bigbazaar admin and sys admin. this is however quite confusing to the user which i keep noticing in trainings.

The concept of multi-tenancy enables us to have several clients within the same database. the user with a System Administrator role normally should not be able to access individual clients (companies), therefore not have access to Client Admin roles.

I propose to remove the Openbravo user and introduce two different users for demo data of Openbravo:
- bigbazaarAdmin with access to the admin, finance, sales, etc role of Bigbazaar
- sysAdmin that has access only to the System Administrator role
Steps To Reproduce
Proposed Solution
Additional Information
TagsReleaseCandidate
Relationships
related to feature request 0007978 closed psarobe Define new roles and create new users in demo data 
related to feature request 0008552 new iciordia Openbravo user should be removed/deactivated 
blocks feature request 0008071 closed psarobe Create a DemoBazaar data set 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2008-07-03 09:47roklenardicNew Issue
2008-07-03 09:47roklenardicAssigned To => cromero
2008-07-03 09:47roklenardicsf_bug_id0 => 2009488
2008-07-07 12:23pjuvaraTag Attached: ReleaseCandidate
2008-07-07 12:23pjuvaraStatusnew => acknowledged
2008-11-10 13:11cromeroAssigned Tocromero => pjuvara
2009-03-11 15:33rafarodaRelationship addedblocks 0008071
2009-03-11 15:34rafarodaRelationship addedrelated to 0007978
2009-04-12 13:35roklenardicRelationship addedrelated to 0008552
2009-07-14 12:23roklenardicNote Added: 0018216
2009-09-01 09:14roklenardicRelationship addedblocks 0010399
2009-09-04 19:35dmitry_mezentsevNote Added: 0019473
2011-02-04 09:11jpabloaeAssigned Topjuvara => rmorley
2011-03-03 23:33pjuvaraStatusacknowledged => scheduled
2011-03-03 23:33pjuvarafix_in_branch => pi
2011-03-03 23:33pjuvaraStatusscheduled => closed
2011-03-03 23:33pjuvaraResolutionopen => no change required

Notes
(0018216)
roklenardic   
2009-07-14 12:23   
This is also highly important to Xpress so please prioritize this together with removing/deactivating Openbravo user.
(0019473)
dmitry_mezentsev   
2009-09-04 19:35   
Hi All,

Because of the decision to proceed with this request in an opposite way: we decided to leave Openbravo user as it is (it is the user everybody knows and everybody knows how to deal with it (change password) and each system has "root" user) but user System was disabled (issue 10447 - now user System is created by default without privilege to log in) I think this one is not a Release Candidate and Blocker for 7978 and 8071 any longer.

I also suggest to close feature request 8552 cause it is doubling this.