summaryrefslogtreecommitdiffstats
path: root/ldap/servers/plugins/syntaxes/numericstring.c
diff options
context:
space:
mode:
authorNathan Kinder <nkinder@redhat.com>2009-10-30 10:28:09 -0700
committerNathan Kinder <nkinder@redhat.com>2009-11-06 08:03:48 -0800
commit07b5f941afb8817c145b8fc73e91c5ea92482948 (patch)
treea95f6adcc3db0ca0be9f70ff545d759de23a0f51 /ldap/servers/plugins/syntaxes/numericstring.c
parentfaf68949bba456988ec4aaa2715c8d9cd664f513 (diff)
downloadds-07b5f941afb8817c145b8fc73e91c5ea92482948.tar.gz
ds-07b5f941afb8817c145b8fc73e91c5ea92482948.tar.xz
ds-07b5f941afb8817c145b8fc73e91c5ea92482948.zip
387681 - Fix errors in mapping AD tombstones
The AD tombstone mapping code is not behaving correctly if a cn contains a comma (such as a "last, first" type value). The code is supposed to locate the first ":" in the tombstone DN, then scan for the first "," after that. Everything between is the GUID. The problem is that the code is starting at the beginning of the string when searching for the "," instead of starting at the ":" that was previously found. This causes the "," in the cn to be found instead, which makes us fail to find the GUID. The fix is to simply start searching for the "," from the ":" in the tombstone DN.
Diffstat (limited to 'ldap/servers/plugins/syntaxes/numericstring.c')
0 files changed, 0 insertions, 0 deletions