[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Inappropriate matching (18): additional info: modify/delete: postalAddress: no equality
- To: openldap-software@OpenLDAP.org
- Subject: Inappropriate matching (18): additional info: modify/delete: postalAddress: no equality
- From: Michael Ströder <michael@stroeder.com>
- Date: Sun, 06 Jul 2008 20:57:39 +0200
- User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.15) Gecko/20080620 SeaMonkey/1.1.10
HI!
using OpenLDAP 2.4.10 (RE24) I'm trying to explicitly delete a value of
attribute postalAddress:
---------------------------------------------------------------
dn: cn=Fred Feuerstein,ou=Testing,dc=stroeder,dc=de
changetype: modify
delete: postalAddress
postalAddress: zeile 1$zeile 2$zeile 3
-
---------------------------------------------------------------
But this results in an error:
modifying entry "cn=Fred Feuerstein,ou=Testing,dc=stroeder,dc=de"
ldapmodify: Inappropriate matching (18)
additional info: modify/delete: postalAddress: no equality
matching rule
But postalAddress is declared in the schema like this:
( 2.5.4.16 NAME 'postalAddress' DESC 'RFC2256: postal address' EQUALITY
caseIgnoreListMatch SUBSTR caseIgnoreListSubstringsMatch SYNTAX
1.3.6.1.4.1.1466.115.121.1.41 )
Aarrgh! What's up with that? If the equality matching rule is not
implemented it should not be announced in the subschema. The server
should not simply report what might have been defined in some RFC.
Background: When generating deltas in web2ldap attribute values are now
explicitly deleted if there's an EQUALITY matching rule defined for an
attribute type. This is done to prevent applying changes in case an
entry and its attributes was changed during the user editing the entry.
Ciao, Michael.