Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 567888

Summary: RFE: add support for posix group tab in console group UI
Product: [Retired] 389 Reporter: Artemy Kapitula, Mail.Ru Cloud Solutions <dalt74>
Component: Directory ServerAssignee: Rich Megginson <rmeggins>
Status: CLOSED DUPLICATE QA Contact: Chandrasekar Kannan <ckannan>
Severity: medium Docs Contact:
Priority: low    
Version: 1.2.6CC: benl, jgalipea, nhosoi, nkinder, rmeggins
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-30 16:23:50 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Artemy Kapitula, Mail.Ru Cloud Solutions 2010-02-24 08:40:32 UTC 
Description of problem:

When creating user from who are the posixUser instance with 389-console, it's possible to activate checkbox in the "Posix user" and define UID, shell and other posixUser attributes. But when creating a group with 389-console, there are no tab or attributes to specify a GID number, and administrator must go into directory service editing and manually append attributes objectclass=posixGroup and gidNumber, that can be annoying when creating several groups:

1. Create a group from "Users and groups" tab
2. Move to "Directories and servers" page
3. Find a server
4. Open "Directory server"
5. Proceed to directory tab
6. Find a group
7. Open properties
8. Click "Advanced" button
9. Add objectclass: posixgroup
10. Set GID number

and if this feature would be enabled, all steps from 2 to 10 will be avoided. Adding objectlass: posixGroup into a group template does not solve problem, because there no field to specify gidNumber in group creation dialog.

Suggestion: when creating user with "useradd" utility, user and group with the same name are created. It can be very usefull in 389-console to have such optional ability.
Comment 1 Martin Kosek 2012-01-04 13:32:18 UTC 
Upstream ticket:
https://fedorahosted.org/389/ticket/91
Comment 2 Rich Megginson 2012-03-30 16:23:50 UTC 

*** This bug has been marked as a duplicate of bug 668950 ***