Introduction
This page describes the way we generate reverse LDIF, for each operations. Reverse LDIF can be applied on a server in order to revert some changes done. The only condition is that they must be played in the exact reverse order.
Prerequisite
Each reverse LDIF must contains a revision number which identify uniquely its order : R-ldif-rev.
Operations
Here are the operations we are considering :
Operation |
AddRequest |
DelRequest |
ModifyRequest |
ModifyDNRequest |
AddRequest
Computing the revert LDIF for an AddRequest is easy : it's a DelRequest where we use the DN of the created entry
DelRequest
To produce a revert LDIF for a DelRequest, we must first read the deleted attribute. We will create a Add Request based on the read deleted entry :
read the entry to be deleted create a revert ldif AddRequest with this deleted entry delete the entry
There is still a question regarding the operational attributes : should we keep them ? How de we guarantee that the creatorName and createTimeStamp attributes are the original ones, instead of the one injected while creating the saved entry ? We will have some impact on the OperationaAttributesInterceptor...