[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Inappropriate matching

To: Schwartz Milan <mschwartz@profitrade.hu>
Subject: Re: Inappropriate matching
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Date: Tue, 31 Oct 2000 08:22:57 -0800
Cc: openldap-software@OpenLDAP.org
In-reply-to: <39FEB9A4.B3F4A802@profitrade.hu>

At 01:23 PM 10/31/00 +0100, Schwartz Milan wrote:
>I'm using the 2.0.6 version of OpenLDAP on Solaris 7. The core, inetorg,
>and cosine schemas are included.
>
>When I try to add a new certificate to an inetOrgPerson object's
>userCertificate;binary attribute (BER encoded, different from the one
>already stored), I got an Inappropriate Matching (18) error code.

The server doesn't support certificate matching.  If the server
is unable to determine whether or not the value to be added already
exists, then it cannot accept the addition.   Use replace (with
old and new values) instead.

>I use the Netscape LDAP JDK 4.1 to manage the directory, the operation
>above succeded on a NS Directory Server 4.1.

Netscape's server must support certificate matching.

References:
- Inappropriate matching
  - From: Schwartz Milan <mschwartz@profitrade.hu>

Prev by Date: Re: zero-length string
Next by Date: Re: use of ObjectClass top
Index(es):
- Chronological
- Thread