Hide Forgot
Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. As admin --> Control panel --> Roles 2. Select all roles and delete 3. Once all roles are deleted , admin cannot perform any operation like creating user etc because of insufficient privileges "You have insufficient privileges to perform action." Actual results: Expected results: Additional info: rpm -qa|grep aeolus aeolus-configure-2.0.1-0.fc14.20110628141215gitb8aaf85.noarch aeolus-conductor-daemons-0.3.0-0.fc14.20110628135944git2a88782.noarch aeolus-all-0.3.0-0.fc14.20110628135944git2a88782.noarch aeolus-conductor-doc-0.3.0-0.fc14.20110628135944git2a88782.noarch rubygem-aeolus-cli-0.0.1-1.fc14.20110628165632git0dfe3ff.noarch aeolus-conductor-0.3.0-0.fc14.20110628135944git2a88782.noarch
At the moment, the right solution here is unclear. From a back end point of view, there are no "magic roles" -- i.e. any role is allowed to be created/deleted, as it's possible that an admin will want to set up a different set of default permissions -- i.e. instead of one role that allows all admin privileges, they might want to split things up into separate roles, none of which can do _everything_. It may be that certain roles should be identified as "non-modifiable" or "un-deletable", but would that flag also be one that couldn't be edited? Should we allow new roles but require that all "default" ones be left alone? That might make the eventual permissions UI confusing with the addition of new roles without being able to remove the defaults.
making sure all the bugs are at the right version for future queries
adding to ce-sprint-next
adding to ce-sprint
removing ce-sprint-next tracker
The UI for 1.0 won't include support for editing roles, including deleting them. So, this is out of scope for 1.0
moving to 1.1
moving version to 1.0.0 . version = found in version
roles can no longer be deleted
Roles can no longer be deleted... good 2 go in CFCE v1.1 2012-09-14.5 puddle
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2012-1516.html