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 867676 - extdom plugin does not handle Posix UID and GID request
Summary: extdom plugin does not handle Posix UID and GID request
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ipa
Version: 6.4
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: rc
: ---
Assignee: Rob Crittenden
QA Contact: Namita Soman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-18 03:46 UTC by Dmitri Pal
Modified: 2013-02-21 09:28 UTC (History)
2 users (show)

Fixed In Version: ipa-3.0.0-6.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-21 09:28:31 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2013:0528 0 normal SHIPPED_LIVE Low: ipa security, bug fix and enhancement update 2013-02-21 08:22:21 UTC

Description Dmitri Pal 2012-10-18 03:46:51 UTC
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/freeipa/ticket/3166

There is some disconnect between sssd and the IPA extdom plugin about how maps a UID or a GID to a SID. Since we try to avoid explicit knowledge of the SID in the client the extdom plugin should map the IDs and the client only sends request with UID and GID. Currently those request are not handled properly.

Comment 1 Martin Kosek 2012-10-18 08:59:04 UTC
Fixed upstream:
master: https://fedorahosted.org/freeipa/changeset/89e315d639e972608df11ae052029aaaf0eb1083
ipa-3-0: https://fedorahosted.org/freeipa/changeset/2b33010a9c5eb734c09582c29c8724ce6eb81d34


Steps to reproduce from Sumit Bose:

1) stop sssd
2) delete all ldb and memory mapped cache files, e.g. 'rm -f /var/lib/sss/mc/* /var/lib/sss/db/*'
3) start sssd
4) call 'getent passwd UID_of_a_user_from_a_trusted_domain'

Comment 3 Scott Poore 2012-11-07 18:35:07 UTC
Verified.

Version ::

ipa-server-3.0.0-7.el6.x86_64
sssd-1.9.2-7.el6.x86_64

Manual Test Results ::

[root@rhel6-1 yum.local.d]# service sssd stop
Stopping sssd:                                             [  OK  ]

[root@rhel6-1 yum.local.d]# rm -f /var/lib/sss/db/* /var/lib/sss/mc/*
rm: cannot remove `/var/lib/sss/db/failure-20121107-1-cache-dbs': Is a directory

[root@rhel6-1 yum.local.d]# service sssd start
Starting sssd:                                             [  OK  ]

[root@rhel6-1 yum.local.d]# getent passwd 1232801136
adtestuser1:*:1232801136:1232801136::/home/adtestdom.com/adtestuser1:

Comment 6 errata-xmlrpc 2013-02-21 09:28:31 UTC
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/RHSA-2013-0528.html


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