Bug #17605
closed
Authorisation system for BE user and groups has logic conflict
0%
Description
In the BE user/group form the rights for content types like "TEXT" have to get removed, while the rights for excludefields, page mounts, file mounts, page types etc. have to get added.
This mix should be solved, so all rights should be additive.The current solution denies a proper additive group/permission concept, and a clear policy would also be much easier to administrate.
ie. one group is for section a which has regular rights, and one group is for advanced users which have additional rights. The section group has no right to add HTML or plugin content elements, and the advanced users group has the right to do that. If I give the group of a section and the group for advanced users to a user, he won't get the rights to add HTML elements. I have to make two user groups for every section just for the content type permissions.
(issue imported from #M6345)
Updated by Martin Kutschker about 17 years ago
Does the setting of BE[explicitADmode] to 'explicitAllow' in the installer do what you want?
Updated by Sonja Schubert about 17 years ago
Thank you, Martin for your answer. I didn't know of this option, I have searched exactly this.
I would suggest that you set this by default, it makes absolutely no sense the other way.
Now, this report is solved, but I don't know how I can change the status.
Updated by Christian Kuhn over 15 years ago
Resolved, no change required as requested by reporter.
Updated by