Summary | LDAP modifiy/delete |
Queue | Turba |
Queue Version | 2.0-RC3 |
Type | Bug |
State | Resolved |
Priority | 1. Low |
Owners | Horde Developers (at) |
Requester | michael.eichenberger (at) stepping-stone (dot) ch |
Created | 12/15/2004 (7481 days ago) |
Due | |
Updated | 12/18/2004 (7478 days ago) |
Assigned | 12/16/2004 (7480 days ago) |
Resolved | 12/18/2004 (7478 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | |
Patch | No |
State ⇒ Resolved
the OpenLDAP core.schema directly:
|The error: "Inappropriate Matching" will be displayed if the
attribute you are trying to delete has no equality rule in the schema.
I had a problem deleting the attribute facsimilieTelephoneNumber,
and it was because my core.schema file did not have an EQUALITY
definition for that attribute. I copied the telephoneNumber EQUALITY
rule and it worked perfectly.|
Before the change:
attributetype ( 2.5.4.23 NAME ( 'facsimileTelephoneNumber' 'fax' )
DESC 'RFC2256: Facsimile (Fax) Telephone Number'
SYNTAX 1.3.6.1.4.1.1466.115.121.1.22 )
After the change:
attributetype ( 2.5.4.23 NAME ( 'facsimileTelephoneNumber' 'fax' )
DESC 'RFC2256: Facsimile (Fax) Telephone Number'
EQUALITY telephoneNumberMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.50{32} )
Not the nicest way to solve the problem, but it works with no side affects!
Assigned to
State ⇒ Assigned
the LDAP server attributes are set up; it doesn't allow it to be empty.
Any idea on how to fix this would be great.
State ⇒ Unconfirmed
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ LDAP modifiy/delete
Queue ⇒ Turba
with a valid fax number. Now I want to remove the fax number, I can't
have an empty value in Turba. I receive the following message in
Horde/Turba: "There was an error updating this entry: Modify failed:
(18) Inappropriate matching".
The corresponding OpenLDAP entries (2.2.19) are as follows:
Dec 15 17:20:51 sbx-017 slapd[15716]: ldbm_modify_internal: delete
Dec 15 17:20:51 sbx-017 slapd[15716]: ldbm_modify_internal: 18
modify/delete: facsimileTelephoneNumber: no equality matching rule
Dec 15 17:20:51 sbx-017 slapd[15716]: send_ldap_result: conn=48 op=3 p=3
Dec 15 17:20:51 sbx-017 slapd[15716]: send_ldap_result: err=18
matched="" text="modify/delete: facsimileTelephoneNumber: noequality
matching rule"
Dec 15 17:20:51 sbx-017 slapd[15716]: send_ldap_response: msgid=4
tag=103 err=18
Dec 15 17:20:51 sbx-017 slapd[15716]: conn=48 op=3 RESULT tag=103
err=18 text=modify/delete: facsimileTelephoneNumber: no equality
matching rule
As a workaround I just pass a white character to the interface :-(