Bug 116227 - Roles are appearing as Groups
Summary: Roles are appearing as Groups
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise CMS
Classification: Retired
Component: APLAWS (Show other bugs)
(Show other bugs)
Version: nightly
Hardware: All Linux
medium
medium
Target Milestone: ---
Assignee: ccm-bugs-list
QA Contact: Daniel Berrange
URL: http://youth.aplaws.org.uk/ccm/conten...
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-02-19 09:30 UTC by James Kearns
Modified: 2007-04-18 17:03 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-02-19 10:16:33 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description James Kearns 2004-02-19 09:30:37 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)

Description of problem:
When I create a new role under the Roles tab, I notice this appears 
in Groups under the User Administration, Groups tab.
Then when I go to Add Members to the Role, search returns these Roles 
as Groups. I expect to set privileges by Role, not Group. 

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Create Role
2. Go to Groups
3. A new Group has appeared
    

Actual Results:  1. Created a role called "Jurassic editor"
2. Can now see a new Group. "Group Name: content Administration 
Jurassic editor"
3. This appears in Member search results for Groups 

Expected Results:  I expect Roles to be different from Groups. One 
would not create the other.

Additional info:

Comment 1 Daniel Berrange 2004-02-19 10:16:33 UTC
Roles are just a convenience in CMS for associating a group with a
bunch of permissions. As such when you create a Role, it internally
creates a group, which you can then see in Groups tab at /ccm/admin.
This is the expected behaviour of the system.



Note You need to log in before you can comment on or make changes to this bug.