Grouper Developers Forum

[Tom Zeller <>]

Before you get too far, a quick check against my local openldap
reminds me that some directory servers support subtree renaming, and
others may not.

For example, given

 ou=stem,dc=edu
   ou=child,ou=stem,dc=edu

I cannot moddn ou=stem since it is non-leaf. And I cannot rename
ou=child first since the parent does not exist yet. I would need to
create a new ou=newStem, move ou=child over to it, then delete
ou=stem. Which would not be renaming. I guess we care about renaming
stems for Active Directory since access privileges may be assigned to
ous, not sure.

Hmm.

On Wed, Nov 2, 2011 at 8:08 AM, Shilen Patel 
<>
 wrote:
> I think the ordering is inconsistent.  I'll fix this to make the stems
> come before the child objects.  Let me know if anybody is expecting the
> opposite order.
>
> Thanks!
>
> -- Shilen
>
> On 11/1/11 7:48 PM, "Tom Zeller" 
> <>
>  wrote:
>
>>When a stem containing child groups is renamed via
>>setExtension("newExtension"), the change log entries for group renames
>>occur before the stem rename.
>>
>>This makes it difficult to rename child groups on a target ldap
>>directory, since the renamed stem (i.e. the OU) has not been renamed
>>yet.
>>
>>Is it possible to change the change log order ? maybe configurably ?
>>
>>Otherwise, I would need to gather all change log events for the stem
>>rename context id, and reorder them somehow, shudder.
>>
>>Thanks,
>>TomZ
>
>