New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
389 DS does not honor the manageDsaIT control on ldapmodify #9
Comments
Comment from nhosoi (@nhosoi) at 2012-01-07 07:46:04 Thanks to Marc for letting me use his IPA system. I could reproduce the problem using his DS managed by IPA. ldapmodify -M -x -D "cn=directory manager" -w -h localhost -p 389dn: uid=keitaro,dc=example,dc=com modifying entry "uid=keitaro,dc=example,dc=com" I stopped in check_entry_for_referral in gdb and went through the stacktrace Without the plugin, we could reach the backend modify function ldbm_back_modify I was hoping to look into the ipa_uuid plugin, but I could not find the package rpm -qf /usr/lib64/dirsrv/plugins/libipa_uuid.so 0 check_entry_for_referral (pb=0x7f66f4004250, entry=0x7f6724003b30, |
Comment from rmeggins (@richm) at 2012-01-10 09:07:47 Is this a 389 bug or an ipa bug? |
Comment from nhosoi (@nhosoi) at 2012-01-10 23:56:49 This is an IPA bug (ipa_uuid). Changed the component of bz 760687 from 389 to freeipa. https://bugzilla.redhat.com/show_bug.cgi?id=760687#c12 817 ret = slapi_search_internal_get_entry(tmp_dn, NULL, &e, (gdb) p ret 818 slapi_sdn_free(&tmp_dn); |
Comment from nkinder (@nkinder) at 2012-08-28 04:14:24 Added initial screened field value. |
Comment from nkinder (@nkinder) at 2017-02-11 23:05:16 Metadata Update from @nkinder:
|
Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/9
https://bugzilla.redhat.com/show_bug.cgi?id=760687
The text was updated successfully, but these errors were encountered: