Project:
View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
ID | ||||||||
0003440 | ||||||||
Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
feature request | [Openbravo ERP] C. Security | minor | always | 2008-01-03 12:53 | 2008-07-15 13:13 | |||
Reporter | alostale | View Status | public | |||||
Assigned To | alostale | |||||||
Priority | normal | Resolution | fixed | Fixed in Version | 2.40 | |||
Status | closed | Fix in branch | Fixed in SCM revision | Unknown | ||||
Projection | none | ETA | none | Target Version | 2.40 | |||
OS | Any | Database | Any | Java version | ||||
OS Version | Database version | Ant version | ||||||
Product Version | SCM revision | |||||||
Merge Request Status | ||||||||
Review Assigned To | ||||||||
OBNetwork customer | No | |||||||
Web browser | ||||||||
Modules | Core | |||||||
Support ticket | ||||||||
Regression level | ||||||||
Regression date | ||||||||
Regression introduced in release | ||||||||
Regression introduced by commit | ||||||||
Triggers an Emergency Pack | No | |||||||
Summary | 0003440: Read only window access for roles | |||||||
Description | Currently it is possible to define a tab as read-only for every role, but the field to do it for different depending on the role which is at Window access tab doesn't work. Tip: This could be implemented using the recently added read-only logic. With this approach there're some issues to be decided: -If this read-only logic is inserted for each field in the application this could affect to the whole application performance. -It could be possible to insert the read-only logic just in case there is at least one role that have not write access. This approach would be more efficient because only those windows that have "read-only roles" would have the javascript logic. The problem is that if access is changed the window would need a recompilation. | |||||||
Tags | No tags attached. | |||||||
Attached Files | ||||||||
![]() |
|
![]() |
|
(0003930) alostale (viewer) 2008-01-25 16:05 edited on: 2008-06-12 09:26 |
Logged In: YES user_id=1500722 Originator: YES In addition this should be implemented at HttpBaseSecureServlet level in order to prevent data modifications not only in interface. |
(0003931) alostale (viewer) 2008-01-25 17:07 edited on: 2008-06-12 09:26 |
Logged In: YES user_id=1500722 Originator: YES http://sourceforge.net/tracker/index.php?func=detail&aid=1833290&group_id=162271&atid=823129 [^] |
(0007029) user71 2005-06-01 00:00 edited on: 2008-06-12 09:44 |
This bug was originally reported in SourceForge bug tracker and then migrated to Mantis. You can see the original bug report in: https://sourceforge.net/support/tracker.php?aid=1863084 [^] |
![]() |
|||
Date Modified | Username | Field | Change |
2008-07-15 13:13 | pjuvara | OBNetwork customer | => No |
2008-07-15 13:13 | pjuvara | Status | new => scheduled |
2008-07-15 13:13 | pjuvara | Target Version | => 2.40 |
2008-07-15 13:13 | pjuvara | Description Updated | |
2008-07-15 13:13 | pjuvara | Status | scheduled => resolved |
2008-07-15 13:13 | pjuvara | Fixed in Version | => 2.40 |
2008-07-15 13:13 | pjuvara | svn_revision | => Unknown |
2008-07-15 13:13 | pjuvara | Resolution | open => fixed |
2008-07-15 13:13 | pjuvara | Status | resolved => closed |
Copyright © 2000 - 2009 MantisBT Group |