Bug #83

Modify condition may be checked instead of modrdn condition in some cases

Added by Jonathan Clarke about 1 year ago. Updated about 1 year ago.

Status:Closed Start:16/06/2009
Priority:Normal Due date:
Assigned to:Jonathan Clarke % Done:

100%
Category:Core
Target version:1.1.0
Problem in version:

Description

If the task.dn property is set in lsc.properties, this is only interpreted after checking which condition to check (create/modify/modrdn). Therefore, is the DN causes a modrdn operation, it may be validated by the modify condition, if and only if the original source DN was identical to the destination DN.

This only affects sync mode, not clean.

Associated revisions

Revision 252
Added by Jonathan Clarke about 1 year ago

Fixes #83. Make sure srcBean is cloned before any checking.

History

Updated by Jonathan Clarke about 1 year ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100

Applied in changeset r252.

Updated by Jonathan Clarke about 1 year ago

  • Status changed from Feedback to Closed

Also available in: Atom PDF