michael@stroeder.com wrote:
Pierangelo Masarati wrote:
michael@stroeder.com wrote:
Looking at the logs slapo-constraint seems to generate a filter which is considered bad by slapd:
constraint_violation uri filter = (&((objectClass=organizationalUnit))(|(ou=Abteilung 1)))
This filter would work and finds the correct entry containing the valid attribute value: (&(objectClass=organizationalUnit)(|(ou=Abteilung 1)))
The overlay assumes you don't put brackets around your filter. This is now fixed in HEAD; please test. p.
First this raises the question what to do if filters are not valid in configuration. I'd prefer if slapo-constraint would cause invalidFilter with an appropriate diagnosticMessage pointing to slapo-constraint configuration to be returned instead of silently assuming the attribute value is wrong.
AFAIK, an invalid filter in the configuration would prevent slapd from starting, although right now checks are not that tight.
Still it does not work for me. The filter seems to be ok now and returns the correct search result. But still the attribute value "Abteilung 1" is not accepted.
Can you provide the filter, the relevant data (or an excerpt of it) and the operation you're trying to perform? I just checked slapo-constraint, after fixing it, and it seemed to work as expected.
p.
Ing. Pierangelo Masarati OpenLDAP Core Team
SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it ----------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Email: ando@sys-net.it -----------------------------------