Bug 805188

Summary: [RFE] "ipa migrate-ds" ldapsearches with scope=1
Product: Red Hat Enterprise Linux 7 Reporter: Dmitri Pal <dpal>
Component: ipaAssignee: Martin Kosek <mkosek>
Status: CLOSED ERRATA QA Contact: Namita Soman <nsoman>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 7.0CC: akasurde, ekeck, mkosek, pvoborni
Target Milestone: rcKeywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ipa-4.2.0-0.1.alpha1.el7 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-19 12:00:20 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
ipa-migrate-ds-scope.log
none
subtree.ldif none

Description Dmitri Pal 2012-03-20 16:19:32 UTC 
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/freeipa/ticket/2547

Hi,
as I reported on the mailing list:
https://www.redhat.com/archives/freeipa-users/2012-March/msg00191.html

The migrate-ds procedure assume that on the source LDAP server ou=people and ou=groups subtrees are flat (they are actually searched with scope=1) while, for example in my deploy, there could be a lot of nested OUs under which to find entries.

I would like the possibility to search in nested ou's.
Comment 2 Petr Vobornik 2015-06-05 17:33:45 UTC 
Fixed upstream
master:
https://fedorahosted.org/freeipa/changeset/a57998f51eb8b62052fe021a68503eed4714c6d3
Comment 5 Abhijeet Kasurde 2015-09-23 10:05:02 UTC 
Created attachment 1076147 [details]
ipa-migrate-ds-scope.log
Comment 6 Abhijeet Kasurde 2015-09-23 10:08:22 UTC 
Created attachment 1076149 [details]
subtree.ldif
Comment 7 Abhijeet Kasurde 2015-09-23 10:09:19 UTC 
Verified.

IPA server version : ipa-server-4.2.0-11.el7.x86_64
Comment 8 errata-xmlrpc 2015-11-19 12:00:20 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.

https://rhn.redhat.com/errata/RHBA-2015-2362.html