*** Before acting on this email or opening any attachment you are advised to read the disclaimer at the end of this email ***
Some questions about the back-meta...
1.
According to ITS 3785, any filter that cannot be successfully parsed is rewritten to include "(!(objectClass=*))" before being propagated to any target, always producing an empty result. My problem is that one of my target servers throws a wobbly when it receives a query with this filter, and takes around 15 seconds to respond with the empty result. Is there any way of circumventing this behaviour?
2.
Two of the target servers return search references for every query. As these are of no use in this application, is there some way to stop openldap from returning these references to the client?
3.
Just out of interest, are there any plans to enable dynamic config functionality for back-meta?
Thanks,
Drew
Andrew Graham AgustaWestland UK andrew.graham@agustawestland.com
*** Disclaimer *** The information contained in this E-Mail and any subsequent correspondence may be subject to the Export Control Act (ECA) 2002. The content is private and is intended solely for the recipient(s). For those other than the recipient any disclosure, copying, distribution, or action taken, or omitted to be taken, in reliance on such information is prohibited and may be unlawful.
If received in error please return to sender immediately.
Under the laws of England misuse of information that is subject to the ECA 2002, is a criminal offence.
Westland Helicopters Ltd Lysander Road Yeovil BA20 2YB England
Registered in England under No 604352
Andrew Graham wrote:
Some questions about the back-meta...
According to ITS 3785, any filter that cannot be successfully parsed is rewritten to include "(!(objectClass=*))" before being propagated to any target, always producing an empty result. My problem is that one of my target servers throws a wobbly when it receives a query with this filter, and takes around 15 seconds to respond with the empty result. Is there any way of circumventing this behaviour?
You could try the "t-f-support" statement; it makes slapd-meta(5) use an "absolute false" (RFC 4526) filter "(|)". You should check whether the remote server(s) support(s) it. As an alternative, invalid filters could be ignored, but this is not possible right now. You could submit a feature request (via the ITS http://www.openldap.org/its/).
Two of the target servers return search references for every query. As these are of no use in this application, is there some way to stop openldap from returning these references to the client?
No. As this functionality might be generally useful, feel free to submit a feature request via the ITS.
Just out of interest, are there any plans to enable dynamic config functionality for back-meta?
Well, there are some; however, a couple of issues currently prevent me from working at it: the configuration is rather involved compared to other backends, and it might require the use of a configuration subtree rather than just one entry. Furthermore, features like the possibility to run-time modifying the number of targets and their order seems to require significant reworking of slapd-meta internals, which means a lot of effort. As such, it is unlikely that I (or SysNet) undertake this without some sponsorship. Of course, patches are welcome as usual.
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 -----------------------------------
openldap-software@openldap.org
-
Andrew Graham -
Pierangelo Masarati