This question has been flagged
1 Reply
6612 Views
actions
Avatar
IBS Group

This is a serious security concern, defining group access rights on menu items is not enough to restrict access to actions

How do you protect against this ? someone could just try action ids one by one until they find an existing action that gives him/her access to potentially private information.

I restricted access to a window action to a specific group, but I was still able to see it with a user that doesn't belong to that group.

Edit: The same goes for views, when I define access rights, they don't work, I can still access them from other groups.

Is this a bug? or am I missing something?

Avatar
Discard
Avatar
Ray Carnes
Best Answer

Using groups to hide or give access to menus is more related to the needs of ergonomics or usability than the needs of security. It is a best practice to putting rules on documents and models instead of putting groups on menus. For example, hiding invoices can be done by modifying the record rule on the invoice object, and it is more efficient and safer than hiding menus related to invoices.

Similarly, using groups to hide or give access to views based on groups should also not be considered as meeting security needs.

From "Security in OpenERP: users, groups" at https://doc.openerp.com/trunk/server/04_security/

Avatar
Discard
IBS Group
Author

Thank your your answer, however your last suggestion does not work, I tested it but I could still access restricted views, the same goes for actions, which is the main thing I am asking about.

Ray Carnes

My suggestion was not to use groups for Views or Actions to meet your security needs.

IBS Group
Author

Assign a group to some window action and try to access it directly through action=ID in the URL from a user that don't belong to that group and you should be able to execute that action and see its results.