diff options
| author | Nathan Kinder <nkinder@redhat.com> | 2009-02-27 21:30:10 +0000 |
|---|---|---|
| committer | Nathan Kinder <nkinder@redhat.com> | 2009-02-27 21:30:10 +0000 |
| commit | 87d07506b1fb1914e88d90e01d3f3a1358b47584 (patch) | |
| tree | 11c546d2d634127b2919d08c6ddc1eea18496a85 /ldap/admin/src/scripts | |
| parent | 3273c5a4327a79ba4a9f49aaf004618b5e17c0ee (diff) | |
| download | ds-87d07506b1fb1914e88d90e01d3f3a1358b47584.tar.gz ds-87d07506b1fb1914e88d90e01d3f3a1358b47584.tar.xz ds-87d07506b1fb1914e88d90e01d3f3a1358b47584.zip | |
Resolves: bug 487725
Bug Description: Performing a MOD operation to bring an entry into
the scope of a DNA managed range doesn't trigger DNA to generate
a new value. This happens since we check the DNA filter against
the existing entry instead of the resulting entry after the mods
are applied.
Reviewed by: rmeggins (thanks!)
Files: see diff
Branch: HEAD
Fix Description: This patch handles modify operations that bring entries
into or out of scope of a managed range. If you bring an entry into scope
(say by adding the appropriate objectclass), this will assign a value from
the range if the magic value or no value is supplied for the managed type.
Platforms tested: F9
Flag Day: no
Doc impact: no
Diffstat (limited to 'ldap/admin/src/scripts')
0 files changed, 0 insertions, 0 deletions
