On Tue, Jul 8, 2008 at 6:24 AM, Michael Ströder <michael(a)stroeder.com> wrote:
Hmm, but then the problem of the original poster is that the matching
rule
applied to an attribute value (based on your rule above) has nothing to with
the normalization of the entry's RDN.
Because he was asking about memberUid=steves vs. memberUid=Steves which are
two different entries in his data (based on caseExactIA5Match) but are
treated as the same entry in FDS.
(Nevertheless he should get his data fixed for various reasons.)
I agree, my schema (and data) are terrible. It's an artifact from
openldap not being as conforming as fds.
My main concern is that sanitizing my repository would require
changing usernames for a hundred odd external users, something I wish
to avoid. But given how memberUid's case sensitivity is nullified when
part of a dn, migration it is.
Thank you all for your help,
Regards,
Mike