[Date Prev][Date Next]
Re: rdnMatch / RDN support (ITS#3207)
> This is a multipart message in MIME format.
> --=_alternative 0082904785256EC1_=
> Content-Type: text/plain; charset="US-ASCII"
> Hi. I am Sang-Seok Lim (Sang) of IBM Watson. I'm currently designing the
> component matching support for OpenLDAP with Jong-Hyuk.
> We interpreted that RDN in RFC3687 means ANY rdn inside a DN which will be
> eventually supported by the component matching.
> For now, we considered both the attribute and assertion values as RDNs.
> This will be changed as we make progress in the component matching
OK, then in this case the rdnNormalize/rdnPretty
are simply extracting the last (leftmost) rdn; I
guess you're still working on extracting other
Another (possibly separated) issue: nameAndOptionalUID,
which is used in uniqueMember, is composed of a DN plus
an optional UID. I wonder if the rdnMatch should apply
to the DN portion of nameAndOptionalUID as well and, in
the case, what actions should be taken (mrd_compat_syntaxes
field in struct slap_mrule_defs_rec? How, and where,
to strip the optional UID to use existing DN/RDN parsing
SysNet - via Dossi,8 27100 Pavia Tel: +390382573859 Fax: +390382476497