Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0003329
TypeCategorySeverityReproducibilityDate SubmittedLast Update
feature request[Openbravo ERP] C. Securityminoralways2007-05-14 18:472012-07-29 14:06
Reporteruser71View Statuspublic 
Assigned Toalostale 
PrioritynormalResolutionfixedFixed in Version3.0MP9
StatusclosedFix in branchpiFixed in SCM revisionMP9
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned To
Web browser
ModulesCore
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0003329: Field permissions.

DescriptionHi!

I think that it would be a good idea to add the access permissions scheme a new level: the field level. Explanation: now you can control access to a windows depending on the role of the user, but not to the fields in that window, so when you need one role to access this windows but with some fields disabled you have to create a "clone" window without those fields. This is a pain (you know where :-P).

I understand that managing permissions to the field level would be a rather difficult task, so I suggest that when you give a role permissions to a window (or tab) you give permission to all its fields, so you have to explicitly tell Openbravo which fields should be disabled (or not shown) only for the roles you need to.

Another suggestion: maybe it would be easier to implement if you could just mark a window (or tab) to be read-only for some roles. This is not as flexible as the field-level access control, but it would do in some cases.

Best regards!!



TagsReleaseCandidate
Attached Files

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
(0006918)
user71
2005-06-01 00:00
edited on: 2008-06-12 09:43

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=1718786 [^]
(0050973)
dmitry_mezentsev (developer)
2012-07-29 14:06

http://wiki.openbravo.com/wiki/Release_Notes/3.0MP9 [^] Extend Openbravo Security Model.

- Issue History
Date Modified Username Field Change
2008-07-01 19:57 pjuvara Assigned To user71 => iciordia
2008-07-01 19:57 pjuvara Status new => acknowledged
2008-07-01 19:57 pjuvara Tag Attached: ReleaseCandidate
2008-11-16 07:44 pjuvara Assigned To iciordia => pjuvara
2008-11-16 08:13 pjuvara Category 01. General setup => C. Security
2008-11-16 08:13 pjuvara Description Updated
2009-05-22 19:36 pjuvara Assigned To pjuvara => iciordia
2012-07-29 14:05 dmitry_mezentsev Status acknowledged => scheduled
2012-07-29 14:05 dmitry_mezentsev Assigned To iciordia => alostale
2012-07-29 14:05 dmitry_mezentsev fix_in_branch => pi
2012-07-29 14:06 dmitry_mezentsev Note Added: 0050973
2012-07-29 14:06 dmitry_mezentsev Status scheduled => resolved
2012-07-29 14:06 dmitry_mezentsev Fixed in Version => 3.0MP9
2012-07-29 14:06 dmitry_mezentsev Fixed in SCM revision => MP9
2012-07-29 14:06 dmitry_mezentsev Resolution open => fixed
2012-07-29 14:06 dmitry_mezentsev Status resolved => closed


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker