directory-api mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Radovan Semancik <radovan.seman...@evolveum.com>
Subject caseIgnoreIA5Match and normalizers
Date Thu, 20 Oct 2016 15:57:38 GMT
Hi,

I'm a bit puzzled about the matching rules and normalizers. I have 
ordinary RFC4519 attribute, let's say it is 'dn':

attributetype ( 0.9.2342.19200300.100.1.25 NAME ( 'dc' 'domainComponent' )
         DESC 'RFC1274/2247: domain component'
         EQUALITY caseIgnoreIA5Match
         SUBSTR caseIgnoreIA5SubstringsMatch
         SYNTAX 1.3.6.1.4.1.1466.115.121.1.26
         SINGLE-VALUE
         USAGE userApplications )

Now when I parse that schema and look at quality matching rule and its 
normalizer it is this:

NORMALIZER ( 1.3.6.1.4.1.1466.109
.114.2
  FQCN
  )

... and it is an instance of NoOpNormalizer class. As this is is 
case-ignore attribute I would expect normalizer that will convert the 
value case. Am I right? Or is there really reason for NoOpNormalizer?

The NoOpNormalizer causes that the values in the DN are not normalized. 
And therefore DNs such as dc=EXAMPLE,dc=COM and dc=example,dc=com are 
considered to be different.

-- 
Radovan Semancik
Software Architect
evolveum.com


Mime
View raw message