RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 698240 - IPA is allowing multiple groups to contain the same gidNumber value
Summary: IPA is allowing multiple groups to contain the same gidNumber value
Keywords:
Status: CLOSED DUPLICATE of bug 693483
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: doc-Identity_Management_Guide
Version: 6.1
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: 6.2
Assignee: Deon Ballard
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On: 697887 698671
Blocks: IPA62DOC
TreeView+ depends on / blocked
 
Reported: 2011-04-20 14:04 UTC by Jenny Severance
Modified: 2011-07-14 22:33 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 697887
Environment:
Last Closed: 2011-07-14 22:33:30 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Jenny Severance 2011-04-20 14:04:10 UTC 
+++ This bug was initially created as a clone of Bug #697887 +++

Description of problem:
I had created a user "tim" with UID 800 which was put in the ipausers group. Then I created a group "staff" with GID 800. What I didn't know is that the user creation silently created a group "tim" which also had the GID 800, which I didn't expect.

So I ended up with two groups with GID 800. Doing "id tim" on the console then only shows the numeric GID, not any of the two names.

Version-Release number of selected component (if applicable):
freeipa-server-2.0.0-1.fc15.x86_64


Steps to Reproduce:
1. Create user "test" with UID 800
2. Create group "testgroup" with GID 800
3. Do "ipa group-find" and "ipa group-find --private"
  
Actual results:
Two groups with GID 800 and different names

Expected results:
The creation of the second group should have reported an error.

--- Additional comment from mkosek on 2011-04-20 08:26:01 EDT ---

Upstream ticket:

https://fedorahosted.org/freeipa/ticket/1183

--- Additional comment from jgalipea on 2011-04-20 10:03:24 EDT ---

This is reproducible:

# ipa user-add --first=Jenny --last=Galipeau --uid=800 --gidnumber=800 jennyg
-------------------
Added user "jennyg"
-------------------
  User login: jennyg
  First name: Jenny
  Last name: Galipeau
  Full name: Jenny Galipeau
  Display name: Jenny Galipeau
  Initials: JG
  Home directory: /home/jennyg
  GECOS field: jennyg
  Login shell: /bin/sh
  Kerberos principal: jennyg@TESTRELM
  UID: 800
  GID: 800

# ipa group-add --desc="test bug 697887" --gid=800 grp697887
-----------------------
Added group "grp697887"
-----------------------
  Group name: grp697887
  Description: test bug 697887
  GID: 800

# id jennyg
uid=800(jennyg) gid=800 groups=800,972400001(ipausers)
Comment 4 Tim Niemueller 2011-05-13 21:57:30 UTC 
Do I read this correctly that there will be no proper technical solution preventing this from happening but to hide it in some footnote or box in the documentation?
Comment 5 Dmitri Pal 2011-05-13 22:38:48 UTC 
Nobody is hiding anything. There is really no technical way to prevent all sorts of different misconfigurations with UID & GID if you decide to override them manually. IPA will do the right thing if you let if deal with UID and GID but if you have to set it up the way you want IPA should not prevent you from doing it.

There are a lot of use cases where for compatibility people would want to mess with GID and UID. We would let them do it but explain the implications and potential problems in the documentation that that they are aware about the problems that their actions might cause. 

It is the best solution we can offer.
Do you still disagree?
Comment 6 Tim Niemueller 2011-05-14 15:15:19 UTC 
I would rather like the tool to check if the UID/GID exists, and if it does throw an error. A "force" flag would then allow the admin to override this if he knows what it is doing.

What this does it that it catches a behavior which I presume is most often undesired and unexpected, but still allows it if the admin know what he is doing. Much better than having this in the documentation, which -- let's be honest -- you hardly read from start to end. If the RHEL documentation is similar to the Fedora Guide I admit that it is excellent and helpful documentation, but I tend to read the least amount of documentation as possible and expect tools to help me, to give relevant and useful run-time information, and to prevent typical pitfalls.

Makes sense?
Comment 7 Rob Crittenden 2011-05-16 14:17:13 UTC 
The default behavior of IPA is to let it assign UID/GID so we give the benefit of the doubt if the user provides it. I opened an RFE ticket to do the enforcement and provide a --force override.

https://fedorahosted.org/freeipa/ticket/1231
Comment 8 Deon Ballard 2011-06-02 18:44:03 UTC 
Blocking the IPA 2.1 tracker bug.
Comment 9 Deon Ballard 2011-07-14 22:33:30 UTC 

*** This bug has been marked as a duplicate of bug 693483 ***
Note You need to log in before you can comment on or make changes to this bug.