[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Searching self-defined attributes
- To: openldap-software@OpenLDAP.org
- Subject: Searching self-defined attributes
- From: lionel poussin <lionel.poussin@gmail.com>
- Date: Mon, 14 Feb 2005 10:55:51 +0100
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=kVNAN53IUrRoIeuiXj7dYl+bTa35AvWOt6AHHIPj3iw5RcstWBUE0yVUi79P3WrAAqL0Nq3KV0CjodAq2flOdehw6DkB8WdM08COMgzPawY38NNb0beBs4Gcqtttmi4T4y/3HgBN5WZ7qOpcUgi4L73bmNwgOIyKjVSY4NYcJV4=
For a web site user management, We've derived a schema from inetorgperson.
All attributes work fine as of storing and retrieving information.
But, for instance with the following attribute, search even in command
line on the server itself is failing.
If we search for (memberNetwork=*), we retrieve all the users that
have the attribute set, but if for instance we search for
(memberNetwork=92), knowing that some users have the attribute set to
that value, it fails.
We suspect it's related to the way we defined the attribute, but infos
fetched by google searching so far didn't help us. Here's how we
defined it:
---
Attributetype ( 1.1.2.1.6
NAME 'memberNetwork'
DESC 'Network appartenance of a member'
EQUALITY octetStringMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.40)
---
If anyone has an idea, or a precise refrence to relevant information
we could read, the dev team here would be most grateful.
Lionel POUSSIN
lionel.poussin@gmail.com