You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to use delete_tree to remove an entire OU and all subordinate objects that may be there.
When I try I get subordinate objects must be deleted first
The only difference between delete and delete_tree is that delete_tree adds the control code 1.2.840.113556.1.4.805 to the delete request. That's all fine, but my server apparently doesn't include that code.
I'm thinking the delete_tree method should conditionally use DELETE_TREE if the server includes it in it's :supportedcontrol array, and if not it should manually recurse the tree deleting everything. If I do ldapdelete -r blah blah from the commandline I'm able to do what I'm attempting with Net::LDAP's delete_tree, so I know it's possible.
Does this sound like a good idea? I'd rather build this feature into a Pull request than code it into my specific application.
The text was updated successfully, but these errors were encountered:
That sounds reasonable to me. Have you looked at any other LDAP clients in other languages to see whether they do something similar? What server are you using? I'm curious whether 1.2.840.113556.1.4.805 is commonly implemented.
I'm trying to use
delete_tree
to remove an entire OU and all subordinate objects that may be there.When I try I get
subordinate objects must be deleted first
The only difference between
delete
anddelete_tree
is thatdelete_tree
adds the control code1.2.840.113556.1.4.805
to the delete request. That's all fine, but my server apparently doesn't include that code.I'm thinking the delete_tree method should conditionally use DELETE_TREE if the server includes it in it's
:supportedcontrol
array, and if not it should manually recurse the tree deleting everything. If I doldapdelete -r blah blah
from the commandline I'm able to do what I'm attempting with Net::LDAP's delete_tree, so I know it's possible.Does this sound like a good idea? I'd rather build this feature into a Pull request than code it into my specific application.
The text was updated successfully, but these errors were encountered: