OMG!
Assuming the tool will parse the URI at least, can't it say "filtering attributes is not implemented (cowardly refusing to run at all)"? The manual suggests, unsupported parts will just be ignored. I think the manual page should state more clearly that LDAP standard URLs cannot be used. The good thing about standards is that there are so many of them.
Apart from that being able to filter specific attributes would be a nice feature.
Kind regards, Ulrich Windl
-----Original Message----- From: Ondřej Kuzník ondra@mistotebe.net Sent: Friday, April 25, 2025 2:47 PM To: Windl, Ulrich u.windl@ukr.de Cc: openldap-technical@openldap.org Subject: [EXT] Re: LDAP URI for slapcat -H
On Fri, Apr 25, 2025 at 07:24:56AM +0000, Windl, Ulrich wrote:
Hi!
After reading the manual of slapcat (for 2.5) it recommends using option -H and an URI instead of other obsolete options. So I tried it, but all I get is a usage message, even with "-v" and "-d9". Like this: # slapcat -d9 -H 'ldap:///?entryCSN?sub?(objectClass=*)' usage: slapcat [-v] [-d debuglevel] [-f configfile] [-F configdir] [-o
<name>[=<value>]] [-c]
[-g] [-n databasenumber | -b suffix] [-l ldiffile] [-a filter] [-s subtree] [-Hurl]
However when I use # slapcat -H 'ldap://?entryCSN?dc=...,dc=de?sub?(objectClass=*)'
In the manpage under the -H option: "use dn, scope and filter from URI to only handle matching entries."
You are adding other parts to the URI (an attribute list) that slapcat is not willing to handle.
Regards,
-- Ondřej Kuzník Senior Software Engineer Symas Corporation http://www.symas.com Packaged, certified, and supported LDAP solutions powered by OpenLDAP