Bug 805188 - [RFE] "ipa migrate-ds" ldapsearches with scope=1
[RFE] "ipa migrate-ds" ldapsearches with scope=1
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa (Show other bugs)
Unspecified Unspecified
medium Severity unspecified
: rc
: ---
Assigned To: Martin Kosek
Namita Soman
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2012-03-20 12:19 EDT by Dmitri Pal
Modified: 2015-11-19 07:00 EST (History)
4 users (show)

See Also:
Fixed In Version: ipa-4.2.0-0.1.alpha1.el7
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-11-19 07:00:20 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
ipa-migrate-ds-scope.log (3.30 KB, text/plain)
2015-09-23 06:05 EDT, Abhijeet Kasurde
no flags Details
subtree.ldif (5.40 KB, text/plain)
2015-09-23 06:08 EDT, Abhijeet Kasurde
no flags Details

  None (edit)
Description Dmitri Pal 2012-03-20 12:19:32 EDT
This bug is created as a clone of upstream ticket:

as I reported on the mailing list:

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 13:33:45 EDT
Fixed upstream
Comment 5 Abhijeet Kasurde 2015-09-23 06:05 EDT
Created attachment 1076147 [details]
Comment 6 Abhijeet Kasurde 2015-09-23 06:08 EDT
Created attachment 1076149 [details]
Comment 7 Abhijeet Kasurde 2015-09-23 06:09:19 EDT

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


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