Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0029213Openbravo ERP09. Financial managementpublic2015-03-06 14:512015-03-13 11:43
Reporterjonalegriaesarte 
Assigned ToAugustoMauch 
PriorityhighSeveritymajorReproducibilityhave not tried
StatusclosedResolutioninvalid 
PlatformOS5OS Version
Product Version 
Target Version3.0PR15Q3Fixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customerOBPS
Web browser
ModulesCore
Support ticket34118
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0029213: Account selector in General ledger report can not be used depending on the permissions to the role
DescriptionAccount selector in General ledger report can not be used depending on the permissions to the role. This makes the report not usable
Steps To Reproduce- Create a testing role, set as manual
- Provide access to org F&B España, user Openbravo and General ledger report
- Logout and login using the new role
- Access to report and try to use the selector. System provides an error.
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
blocks design defect 0029175 acknowledged AugustoMauch Account selector in General ledger report can not be used depending on the permissions to the role 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2015-03-10 11:06jorge-garciaTypedefect => backport
2015-03-11 13:34vmromanosAssigned ToSandrahuguet => AugustoMauch
2015-03-11 13:34vmromanosNote Added: 0075446
2015-03-13 11:43alostaleNote Added: 0075535
2015-03-13 11:43alostaleStatusscheduled => closed
2015-03-13 11:43alostaleResolutionopen => invalid

Notes
(0075446)
vmromanos   
2015-03-11 13:34   
Forward to platform:

Problem found in HttpSecureAppServlet.java, method hasGeneralAccess().

The SeguridadData.selectAccessSearch() query only takes into account Windows, but this is a Report, so no ad_window_access is found.

Proposed solution: Query should be changed, or alternatively hack in hasAccess() method to control that situation.



Note that other selectors (Multiple Business Partner, Project, etc.) show data in this scenario, so this selector must have the same logic.
(0075535)
alostale   
2015-03-13 11:43   
backport not required