Recent changes to feature-requests

#18 be more lenient in LDIFParser

Michael Ströder — Fri, 09 Dec 2016 07:32:09 -0000

status: open --> closed
assigned_to: Michael Ströder
Group: -->

#10 support for winldap

Michael Ströder — Mon, 29 Feb 2016 17:46:10 -0000

status: open --> wont-fix
discussion: enabled --> disabled
Group: -->

#5 LDIF parser hides DN with change record type

Michael Ströder — Fri, 05 Feb 2016 09:19:40 -0000

status: open --> closed
assigned_to: Michael Ströder
Group: -->

be more lenient in LDIFParser

Jephte CLAIN — Wed, 03 Feb 2016 16:25:35 -0000

hello,

from the "be lenient with what you parse, be strict with what you write" departement, I attach a patch which support ldif input with several blank and/or comment lines between objects
I don't know if this behavior is correct wrt the LDIF standard, but it is useful for me, because I have LDIF files with comments written by humans, e.g:

# silly example
dn: uid=one,dc=tld
uid: one

# another silly example
dn: uid=two,dc=tld
uid: two

with the current parser, uid=two is not read because there are two "blanks" lines before

best regards,
Jephte CLAIN

be more lenient in LDIFParser

Jephte CLAIN — Wed, 03 Feb 2016 16:25:35 -0000

Ticket 18 has been modified: be more lenient in LDIFParser
Edited By: Michael Ströder (stroeder)
Status updated: u'open' => u'closed'
Owner updated: None => u'stroeder'

modlist value replacement

Anonymous — Thu, 31 May 2012 21:15:39 -0000

Did not like how modifyModlist handled the case where there were old and new multi valued attribute differences. Delete all and then just add all the values from old? works, but when you have a million values and you only need to change a few, it's a bit of extra work.
Attached is my version of modlist.py that only deletes or adds what is different. Used the 2.4.9 version as the base I modified.
Done some testing, but it's not extensively tested.

New Feature: support ldap_extended_operation

Anonymous — Fri, 01 Oct 2010 17:40:42 -0000

python-ldap should provide a way to call ldap_extended_operation to call arbitrary extended operations (e.g. perhaps an extop method to LDAPObject?)
A patch has been submitted to add support for returning extended operation responses. This would allow python-ldap to be used for a much wider variety of applications (e.g. a general purpose openldap LDAPSync client).

[PATCH] OpenLDAP OPT_DEFBASE Support (new patch / comment)

Johannes Weißl — Mon, 20 Sep 2010 16:31:39 -0000

Sorry for sending a duplicate feature request to 2185369, but I could somehow not comment on it. They can be merged if possible!

stroeder wrote on 2008-11-20 16:49:44 CET:
> Can you please elaborate which versions of the OpenLDAP libs supports this
> option?
> In general I'm not in favor of letting Python apps rely on ldap.conf since
> this proprietary OpenLDAP configuration concept is widely misused.

LDAP_OPT_DEFBASE seems to be supported since Tue Apr 25 20:23:01 2006 UTC [1] [2]. The oldest release on the FTP which I could find was 2.4.6 (released on 2007/10/31). I updated the patch to current CVS and also included ifdefs for older versions of openldap. I would suggest accepting the patch,
since it doesn't mean Python apps rely on ldap.conf (since the default basedn could be overwritten by command line args to the application). Also options like LDAP_OPT_URI (which can be set in ldap.conf) are already supported.

Greetings,
Johannes

Support for reading controls sent with LDAP_RES_SEARCH_ENTRY

Anonymous — Wed, 29 Jul 2009 15:53:00 -0000

There doesn't appear to be a way to get the controls returned with LDAP_RES_SEARCH_ENTRY responses from the server. It looks like the code in l_ldap_result3() only grabs the controls sent with the result response, not search entry or search references responses:

978 if (res_type == LDAP_RES_SEARCH_ENTRY
979 || res_type == LDAP_RES_SEARCH_REFERENCE
980 )
981 pmsg = LDAPmessage_to_python( self->ldap, msg );
982 else {
983 int result;
984 char **refs = NULL;
985 LDAPControl **serverctrls = 0;
986 LDAP_BEGIN_ALLOW_THREADS( self );
987 ldap_parse_result( self->ldap, msg, &result, NULL, NULL, &refs,
988 &serverctrls, 0 );

The ability to read per-entry controls is necessary to support features like the new Dereference control http://www.openldap.org/devel/cvsweb.cgi/~checkout~/doc/drafts/draft-masarati-ldap-deref-xx.txt, persistent search, and probably other features.

[PATCH] OpenLDAP OPT_DEFBASE Support

Anonymous — Tue, 21 Oct 2008 20:39:35 -0000

Later versions of OpenLDAP (this patch was tested against OpenLDAP 2.4.11) support the LDAP_OPT_DEFBASE option, which returns the value for basedn set in the ldap.conf file.

This patch modifies constants.c and options.c so that ldap.OPT_DEFBASE can be used as an argument to ldap.get_option().