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 785201 - AD Users synced to IPA server are not added to "ipausers" group
Summary: AD Users synced to IPA server are not added to "ipausers" group
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa
Version: 7.0
Hardware: All
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: Martin Kosek
QA Contact: IDM QE LIST
URL:
Whiteboard:
Depends On:
Blocks: 803052
TreeView+ depends on / blocked
 
Reported: 2012-01-27 15:44 UTC by Niranjan Mallapadi Raghavender
Modified: 2015-01-21 15:08 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 803052 (view as bug list)
Environment:
Last Closed: 2015-01-21 15:08:19 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Niranjan Mallapadi Raghavender 2012-01-27 15:44:29 UTC 
Description of problem:

When Windows Active Directory Users are synced to IPA server, the AD user is not added as a member of "ipausers" . 

As per the ipa-winsync configuration on ipa server, ipawinsyncdefaultgroupattr: ipaDefaultPrimaryGroup

and ipaDefaultPrimaryGroup is "ipausers"

dn: cn=ipa-winsync,cn=plugins,cn=config
objectClass: top
objectClass: nsSlapdPlugin
objectClass: extensibleObject
cn: ipa-winsync
nsslapd-pluginPath: libipa_winsync
nsslapd-pluginInitfunc: ipa_winsync_plugin_init
nsslapd-pluginDescription: ipa winsync plugin
nsslapd-pluginId: ipa-winsync-plugin
nsslapd-pluginVersion: FreeIPA/1.0
nsslapd-pluginVendor: FreeIPA project
nsslapd-pluginType: preoperation
nsslapd-pluginEnabled: on
nsslapd-plugin-depends-on-type: database
ipawinsyncrealmfilter: (objectclass=krbRealmContainer)
ipawinsyncrealmattr: cn
ipawinsyncnewentryfilter: (cn=ipaConfig)
ipawinsyncnewuserocattr: ipauserobjectclasses
ipawinsyncuserflatten: true
ipawinsynchomedirattr: ipaHomesRootDir
ipawinsyncloginshellattr: ipaDefaultLoginShell
ipawinsyncdefaultgroupattr: ipaDefaultPrimaryGroup
ipawinsyncdefaultgroupfilter: (gidNumber=*)(objectclass=posixGroup)(objectclas
 s=groupOfNames)
ipawinsyncacctdisable: both
ipawinsyncforcesync: true
ipawinsyncuserattr: uidNumber 999
ipawinsyncuserattr: gidNumber 999



After the AD user is synced, the gidNumber is same as the uidNumber i.e alloted to AD User. 

Example, Below is the entry of the ADUser that is synced from Windows 2008 Server.

dn: uid=rhipauser1,cn=users,cn=accounts,dc=iris,dc=gsslab,dc=pnq,dc=redhat,dc=
 com
mepManagedEntry: cn=rhipauser1,cn=groups,cn=accounts,dc=iris,dc=gsslab,dc=pnq,
 dc=redhat,dc=com
objectClass: top
objectClass: person
objectClass: organizationalperson
objectClass: inetOrgPerson
objectClass: ntUser
objectClass: inetuser
objectClass: posixaccount
objectClass: krbprincipalaux
objectClass: krbticketpolicyaux
objectClass: ipaobject
objectClass: mepOriginEntry
ntUserDeleteAccount: true
uid: rhipauser1
sn: user1
givenName: rhipa
initials: rh
cn: rhipauser1
ntUserCodePage: 0
ntUserAcctExpires: 9223372036854775807
ntUserDomainId: rhipauser1
ntUniqueId: 3ac04b5c42927642b4531edf54072c3f
krbPrincipalName: rhipauser1.PNQ.REDHAT.COM
homeDirectory: /home/rhipauser1
gecos: rhipauser1
loginShell: /bin/sh
uidNumber: 1297200004
gidNumber: 1297200004
ipaUniqueID: f75d6f70-494e-11e1-a08b-5254005a4de1



Version-Release number of selected component (if applicable):
ipa-server-2.1.3-9.el6.x86_64

How reproducible:


Steps to Reproduce:
1. Configure Windows AD Sync 
ipa-replica-manage connect --winsync --binddn cn=rhipasyncuser,cn=Users,dc=iris,dc=gsslab,dc=pnq,dc=redhat,dc=com --bindpw 1redsmB --passsync redhat@123 --cacert /etc/openldap/cacerts/certnew.cer --win-subtree ou=ipa,dc=iris,dc=gsslab,dc=pnq,dc=redhat,dc=com irene.iris.gsslab.pnq.redhat.com -v

2. Create users on AD  under "ou=ipa,dc=iris,dc=gsslab,dc=pnq,dc=redhat,dc=com " on Windows Server. 

3. The AD user on IPA will not be a member of "ipausers" group

  
Actual results:

 The AD user on IPA will not be a member of "ipausers" group

Expected results:

 The AD user on IPA should be a member of "ipausers" group

Additional info:
Comment 2 Martin Kosek 2012-01-30 08:05:33 UTC 
Upstream ticket:
https://fedorahosted.org/freeipa/ticket/2324
Comment 10 Martin Kosek 2015-01-21 15:08:19 UTC 
Thank you taking your time and submitting this request for Red Hat Enterprise Linux. Unfortunately, this bug was not given a priority and was deferred both in the upstream project and in Red Hat Enterprise Linux.

Given that we are unable to fulfill this request in following Red Hat Enterprise Linux releases, I am closing the Bugzilla as DEFERRED. To request that Red Hat re-considers the decision, please re-open the Bugzilla via appropriate support channels and provide additional business and/or technical details about its importance to you.

Note that you can still track this request or even contribute patches in the referred upstream Trac ticket.
Note You need to log in before you can comment on or make changes to this bug.