Works fine with IPA 4.1.2 in ovirt 3.6.
Btw, I can see that for RHDS it takes the namingContext as well, not defaultNamingContext, worth to fix?
389 has defaultNamingContext as far as I know.
$ ldapsearch -H ldap://ldap.corp.redhat.com -b '' -s BASE -x -LLL defaultNamingContext
Yes, but engine uses namingContext, not defaultNamingContext. So we have same issue as with IPA.
(In reply to Ondra Machacek from comment #9)
> Yes, but engine uses namingContext, not defaultNamingContext. So we have
> same issue as with IPA.
oh! I thought the other way around.
I truly do not think we should fix this legacy provider any more.
the ipa fix was because of a change in ipa for existing customers.
not my decision though.
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.