"create" permission in res.users dont work with other users, not admin
Bug #1021378 reported by
Evelyn Martinez
This bug affects 29 people
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Odoo Server (MOVED TO GITHUB) |
Fix Released
|
Medium
|
OpenERP's Framework R&D | |||
OpenERP Community Backports (Server) | Status tracked in 7.0 | |||||
7.0 |
Fix Released
|
Medium
|
Stefan Rijnhart (Opener) | |||
Therp Backports (Deprecated) |
Fix Released
|
Low
|
Stefan Rijnhart (Opener) | |||
Server-6.1 |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
When you create a new user and give permissions: Administration: "access rights". This group "access rights" has create permission to res.users table.
Then login with this new user and try to create a new user, it dont work, the message is "Access Error Operation:
The result I expected was create a new user, by using a user different to admin, that has "access rights" permissions.
The platform is ubuntu
The Openerp Version is 6.1 rev. 4196
Related branches
lp:~openerp-dev/openobject-server/trunk-bug-1021378-aja
- Nicholas Riegel (community): Needs Fixing
- Olivier Dony (Odoo): Approve
- Yannick Vaucher @ Camptocamp (community): Approve (tests)
-
Diff: 18 lines (+1/-1)1 file modifiedopenerp/osv/orm.py (+1/-1)
lp:~therp-nl/therp-backports/server61-lp1021378-fix_record_rule_create_timing
- Therp: Pending requested
-
Diff: 19 lines (+1/-1)1 file modifiedopenerp/osv/orm.py (+1/-1)
lp:~stefan-opener/ocb-server/trunk-bug-1021378-aja
- Alexandre Fayolle - camptocamp: Approve (code review, test.)
- OpenERP Community Backports: Pending requested
-
Diff: 18 lines (+1/-1)1 file modifiedopenerp/osv/orm.py (+1/-1)
Changed in openobject-server: | |
assignee: | nobody → OpenERP's Framework R&D (openerp-dev-framework) |
importance: | Undecided → Medium |
status: | New → Confirmed |
Changed in openobject-server: | |
status: | In Progress → Fix Committed |
Changed in therp-backports: | |
milestone: | none → 6.1-maintenance |
assignee: | nobody → Stefan Rijnhart (Therp) (stefan-therp) |
Changed in therp-backports: | |
status: | New → Fix Committed |
importance: | Undecided → Low |
Changed in therp-backports: | |
status: | Fix Committed → Fix Released |
Changed in therp-backports: | |
milestone: | 6.1-maintenance → 7.0-maintenance |
Changed in therp-backports: | |
milestone: | 7.0-maintenance → none |
no longer affects: | therp-backports/server-7.0 |
tags: | added: maintenance |
To post a comment you must log in.
Hello, /bugs.launchpad .net/openobject -server/ +bug/944813/ +activity
I think this bug results of the changes made here :
https:/
If you don't use multicompanies you can simply solve it by changing back ids','child_ of',[user. company_ id.id]) ] id','child_ of',[user. company_ id.id]) ]
[('company_
to
[('company_
(or just removing the line) in Settings / Security / Record Rules for res.users.
If it can help, this problem occurs because inside orm.py, in the BaseModel create method, the new user is created, then the access rules are checked (so no problem to get the new user company_id), but the inserts into res_company_ users_rel table are not made yet (so we don't get the new user in company_ids). This table is supposed to be filled later in the same method, when the var upd_todo is checked.