Emmanuel Lecharny wrote:
e.g. to find the syntax and what normalization rules it uses. And, whether
you take this approach or not, you need a strategy for dealing with
unrecognized attributeTypes. I.e., right now you're using the OID, but what
happens if you're unable to find the OID?
Another excellent point.
Currently, if the OID is not found, then we consider that the DN is
incorrect, and we throw an error. This is done during the DN
normalization. Is that the correct behavior ? (Assuming that we handle
correctly the referrals and extensible ObjectClass... To be double
checked ! Did I forgot any other case ?)
I think that covers it for DN parsing. Attribute normalization is also needed
for filter evaluation, and in that case, servers are supposed to silently
ignore invalid/unrecognized filter terms.
Thanks for chiming in Howard. It's always good to have your input!
Damn yes !
Glad to be able to help.
More to come on the DN parsing page. I have 4 hours in the train
tomorrow, perfect time to write doco.
Thanks guys !
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
