python-ldap-dev — discussion among developers

Typo error in Demo/Lib/ldap/async/deltree.py (2.3.9)

[Zhang H. <zhb...@gm...>]

Hi, developers.

There's an incorrect module name in Demo/Lib/ldap/async/deltree.py, it  
seems 'ldap.async.SearchHandler' should be replaced by  
'ldap.async.AsyncSearchHandler'.

python-ldap version: 2.3.9.

Thanks for your hard work :)

-- 
Best Regards.

Zhang Huangbin

- Open Source Mail Server Solution for Red Hat(R) Enterprise Linux,
   CentOS, Debian, Ubuntu:
   + http://code.google.com/p/iredmail/
   + http://www.iredmail.org/forum/

Re: version 2.3.8

[Michael S. <mi...@st...>]

Waldemar Osuch wrote:
> On Thu, Jul 9, 2009 at 9:07 AM, Larry kavanagh<lar...@ex...> wrote:
>> Hi ..
>> Triying to install python-ldap-2.3.8 using the EXE on a server (windows
>> 2000)  that has python 2.4.4 installed (or so the plone site tells me)
>>
>> however it won't install and tells me that "python 2.4 required which
>> was not found in the registry"
>>
> I think this is related to how Plone gets installed this days.
> Googling found this:
> http://plone.org/documentation/faq/on-windows-xp-i-get-no-python-installation-found-in-the-registry-when-installing-certain-products-1
> it seems to be relevant.

Waldemar, thanks for pointing us to that issue. It seems to me the
Windows installer for Plone should be fixed.

Ciao, Michael.

Re: version 2.3.8

[Waldemar O. <wal...@gm...>]

On Thu, Jul 9, 2009 at 9:07 AM, Larry kavanagh<lar...@ex...> wrote:
> Hi ..
> Triying to install python-ldap-2.3.8 using the EXE on a server (windows
> 2000)  that has python 2.4.4 installed (or so the plone site tells me)
>
> however it won't install and tells me that "python 2.4 required which
> was not found in the registry"
>
I think this is related to how Plone gets installed this days.
Googling found this:
http://plone.org/documentation/faq/on-windows-xp-i-get-no-python-installation-found-in-the-registry-when-installing-certain-products-1
it seems to be relevant.

Waldemar

Re: version 2.3.8

[Michael S. <mi...@st...>]

Larry,

please note that non-subscriber postings to python-ldap-dev are deferred.

Larry kavanagh wrote:
> Triying to install python-ldap-2.3.8 using the EXE on a server (windows 
> 2000)  that has python 2.4.4 installed (or so the plone site tells me)
> 
> however it won't install and tells me that "python 2.4 required which 
> was not found in the registry"

Which EXE files did you use? It has to exactly match the Python version
used. So for using python-ldap 2.3.8 with Python 2.4 under Win32 it
would be this installer:

http://pypi.python.org/packages/2.4/p/python-ldap/python-ldap-2.3.8.win32-py2.4.exe#md5=35da547711280c18bd4ccd6e637cdf9b

Ciao, Michael.

Re: ANN: python-ldap-2.3.9

[Torsten K. <pyt...@tk...>]

Hi list, hi Michael,

first of all: Michael, thanks for the new release!

Eggs for 2.3.9 are available at

	http://svn.kmrc.de/download/distribution/contrib

In addition to the information given in the section ".egg builds" on

	http://www.python-ldap.org/download.shtml

the following changes apply:

- MacOS X / Linux -> no change in prerequisites
- MacOS X fat eggs have been successfully tested on a freshly
  installed MacOS X 10.4 PPC System.
- The Windows eggs are now statically linked against libsasl2.
  To accomplish this, I used the method described at
	https://wiki.mozilla.org/LDAP_C_SDK_SASL_Windows
  to build the .DLL and then converted it into a static MinGW
  compatible lib by executing (thanks for the hint, Waldemar ;-)

	# pexports.exe -v \
		-h ../include/sasl/sasl.h libsasl.dll >libsasl.def
	# dlltool.exe --input-def libsasl.def \
		--dllname libsasl.dll --output-lib libsasl2.a -k

As always, testers are very welcome, especially for the Win32 SASL
setup!

Best regards,
Torsten
-- 
Executive ability is deciding quickly and getting somebody else to do
the work.
		-- John G. Pollard

ANN: python-ldap-2.3.9

[Michael S. <mi...@st...>]

Find a new release of python-ldap:

  http://www.python-ldap.org/

python-ldap provides an object-oriented API to access LDAP directory
servers from Python programs. It mainly wraps the OpenLDAP 2.x libs for
that purpose. Additionally it contains modules for other LDAP-related
stuff (e.g. processing LDIF, LDAPURLs and LDAPv3 schema).

Ciao, Michael.

-- 
Michael Ströder
E-Mail: mi...@st...
http://www.stroeder.com

----------------------------------------------------------------

Released 2.3.9 2009-07-26

Changes since 2.3.8:

Lib/
* All modules (ldap, ldif, dsml and ldapurl) have common version number now
* Non-exported function ldif.needs_base64() was abandoned and is now
  implemented as method LDIFWriter._needs_base64_encoding().
  This allows sub-classes of LDIFWriter to implement determining whether
  attribute values have to be base64-encoded in a different manner and is
  the same approach like in class dsml.DSMLWriter.
* LDAPUrlExtension._parse() now gracefully handles LDAP URL extensions
  without explicit exvalue as being set with implicit value None.

Modules/
* New LDAP option constant ldap.OPT_X_SASL_NOCANON supported
  in LDAPObject.get/set_option()

To do: LDAPv3 response controls / ldap.LDAPError exceptions

[Michael S. <mi...@st...>]

HI!

In some situations there are controls attached to a LDAP response also
in the case if LDAPResult::resultCode is not success(0). python-ldap
just generates an exception in this case with resultCode,
diagnosticMessage etc. But a calling application might also need to have
access to the controls which might indicate more details why the
operation failed.

One important example for this behaviour are password policy controls
and the bind operation (see [1] and [2]). The response controls define
why the operation failed (e.g. password soon to expire, password reset
needed).

Could somebody with C programming skills please look into how to return
these controls to the calling application via exception?

Also we should look at how response controls can be returned to the
application in case of intermediate responses. E.g. this is needed for
implementing syncrepl in searchAndPersist mode with search requests.

Ciao, Michael.

[1] http://tools.ietf.org/draft/draft-behera-ldap-password-policy/
[2] http://tools.ietf.org/draft/draft-vchu-ldap-pwd-policy/

Re: License for python-ldap

[Michael S. <mi...@st...>]

David,

David Gotz wrote:
> I could not find any mention of a license in the
> documentation for python-ldap.  Can you tell me how
> python-ldap is opensourced?  Is it covered by the Python
> license?  OpenLDAP license? GPL?

It's definitely not GPL. There's a file LICENCE in python-ldap's source
distribution tar.gz.

Basically the intention is that whatever you can do with Python or
whereever you're allowed to deploy Python the same applies to
python-ldap. This could change in the future in such a way that we can
integrate python-ldap into the Python standard lib. Which means: The
license will be probably even more liberal.

You should definitely ask those questions on the python-ldap-dev mailing
list (Cc:-ed).

Ciao, Michael.

Minor changes/improvements for 2.3.9

[Michael S. <mi...@st...>]

HI!

I'm going to release python-ldap 2.3.9 soon. Are there any suggestions
for minor changes/improvements which should be added to this release?

Ciao, Michael.

Re: Egg news :-)

[Torsten K. <pyt...@tk...>]

Hi list,

JFI: during the weekend I had the opportunity to confirm that the
statically linked Mac OS X egg for Python 2.6 works perfectly on a
freshly installed OS X 10.4.11 PPC. Not even XCode is needed.

Now I'm still trying to figure how to get cyrus-sasl working properly
for the Win32 eggs. Waldemar already gave me some hints, but there must
be a clean way to do it without building all of cyrus' dependencies (how
else would the subversion folks manage to survive... ;-)

Best regards
Torsten
-- 
  It's more than magnificent-it's mediocre. -Samuel Goldwyn

Re: Apache DS ignores attrsonly

[Thorsten K. <tho...@th...>]

* Michael Ströder (Mon, 13 Jul 2009 13:23:26 +0200)
> Thorsten Kampe wrote:
> > It does work against eDirectory and Active Directory (as mentioned). 
> 
> ...and OpenLDAP. So the likelihood is very high that python-ldap does
> not have a bug.
> 
> > "ldapsearch -A" also works against Apache DS. The question is still: is 
> > that a Python-LDAP or Apache DS bug?
> 
> It's a ApacheDS bug.
> 
> > Could you install Apache Directory Server or Apache Directory Studio? 
> 
> Hmm, you're very generous with my spare time.

> > Both allow you to create that directory that I queried in about one 
> > minute.
> 
> I did and watching the LDAP traffic with Wireshark shows that ApacheDS
> returns the attribute values although searchRequest::typesOnly is True
> on the wire. In opposite to that OpenLDAP's slapd does not return any
> attribute values in this case.
> 
> I suspect ldapsearch -A also changes the way how found entries are
> displayed.
> 
> Please next time use Wireshark to track things down.

I would have done it if that would be an option. Apart from the fact 
that my Apache DS runs on my local host and winpcap not being able to 
capture packets on the looback interface (on Windows) I am not familiar 
with LDAP enough to be able to judge what "searchRequest::typesOnly" is 
or means.

Nevertheless thanks, I'm going to open a bug with the Apache DS team.

Thorsten

Re: Apache DS ignores attrsonly

[Michael S. <mi...@st...>]

Thorsten Kampe wrote:
> It does work against eDirectory and Active Directory (as mentioned). 

...and OpenLDAP. So the likelihood is very high that python-ldap does
not have a bug.

> "ldapsearch -A" also works against Apache DS. The question is still: is 
> that a Python-LDAP or Apache DS bug?

It's a ApacheDS bug.

> Could you install Apache Directory Server or Apache Directory Studio? 

Hmm, you're very generous with my spare time.

> Both allow you to create that directory that I queried in about one 
> minute.

I did and watching the LDAP traffic with Wireshark shows that ApacheDS
returns the attribute values although searchRequest::typesOnly is True
on the wire. In opposite to that OpenLDAP's slapd does not return any
attribute values in this case.

I suspect ldapsearch -A also changes the way how found entries are
displayed.

Please next time use Wireshark to track things down.

Ciao, Michael.

Re: Apache DS ignores attrsonly

[Thorsten K. <tho...@th...>]

* Michael Ströder (Mon, 13 Jul 2009 11:51:29 +0200)
> Which versions of Python and python-ldap are you using?

Python 2.6.2, python-ldap 2.3.8, Apache DS 1.5.4
 
> I've tested it with my local OpenLDAP server with Python 2.6 and
> python-ldap 2.3.8 built against OpenLDAP RE24 libs:
> 
> >>> l.search_ext_s('dc=stroeder,dc=de',0,'(objectclass=*)',attrsonly=0)
> [('dc=stroeder,dc=de', {'description': ['Wurzeleintrag f\xc3\xbcr
> lokales Adressbuch von Michael Str\xc3\xb6der'], 'labeledURI':
> ['http://www.stroeder.de', 'http://www.block-floete.de'], 'objectClass':
> ['domain', 'labeledURIObject', 'domainRelatedObject'],
> 'associatedDomain': ['stroeder.com'], 'dc': ['stroeder'], 'o':
> ['Michaels'], 'seeAlso': ['dc=stroeder,dc=com']})]
> >>> l.search_ext_s('dc=stroeder,dc=de',0,'(objectclass=*)',attrsonly=1)
> [('dc=stroeder,dc=de', {'description': [], 'labeledURI': [],
> 'objectClass': [], 'associatedDomain': [], 'dc': [], 'o': [], 'seeAlso':
> []})]
> >>> l.search_ext_s('dc=stroeder,dc=de',0,'(objectclass=*)',attrsonly=True)
> [('dc=stroeder,dc=de', {'description': [], 'labeledURI': [],
> 'objectClass': [], 'associatedDomain': [], 'dc': [], 'o': [], 'seeAlso':
> []})]
> 
> So it seems that it simply works.

It does work against eDirectory and Active Directory (as mentioned). 
"ldapsearch -A" also works against Apache DS. The question is still: is 
that a Python-LDAP or Apache DS bug?

Could you install Apache Directory Server or Apache Directory Studio? 
Both allow you to create that directory that I queried in about one 
minute.

Thorsten

Re: Apache DS ignores attrsonly

[Thorsten K. <tho...@th...>]

* Michael Ströder (Mon, 13 Jul 2009 11:20:44 +0200)
> Thorsten Kampe wrote:
> > [4]>>> connection.search_s('ou=system', ldap.SCOPE_SUBTREE, 
> > filterstr='(cn=*)', attrlist = ['cn'], attrsonly = True)
> 
> Just a wild guess: Could you please try again with attrsonly=1. Note
> that this API has its roots in Python 1.x times where there was no
> Boolean True/False type. It would be worth handling that gracefully though.

Same result.

Thorsten

Re: Apache DS ignores attrsonly

[Michael S. <mi...@st...>]

Michael Ströder wrote:
> Thorsten Kampe wrote:
>> [4]>>> connection.search_s('ou=system', ldap.SCOPE_SUBTREE, 
>> filterstr='(cn=*)', attrlist = ['cn'], attrsonly = True)
> 
> Just a wild guess: Could you please try again with attrsonly=1. Note
> that this API has its roots in Python 1.x times where there was no
> Boolean True/False type. It would be worth handling that gracefully though.

Which versions of Python and python-ldap are you using?

I've tested it with my local OpenLDAP server with Python 2.6 and
python-ldap 2.3.8 built against OpenLDAP RE24 libs:

>>> l.search_ext_s('dc=stroeder,dc=de',0,'(objectclass=*)',attrsonly=0)
[('dc=stroeder,dc=de', {'description': ['Wurzeleintrag f\xc3\xbcr
lokales Adressbuch von Michael Str\xc3\xb6der'], 'labeledURI':
['http://www.stroeder.de', 'http://www.block-floete.de'], 'objectClass':
['domain', 'labeledURIObject', 'domainRelatedObject'],
'associatedDomain': ['stroeder.com'], 'dc': ['stroeder'], 'o':
['Michaels'], 'seeAlso': ['dc=stroeder,dc=com']})]
>>> l.search_ext_s('dc=stroeder,dc=de',0,'(objectclass=*)',attrsonly=1)
[('dc=stroeder,dc=de', {'description': [], 'labeledURI': [],
'objectClass': [], 'associatedDomain': [], 'dc': [], 'o': [], 'seeAlso':
[]})]
>>> l.search_ext_s('dc=stroeder,dc=de',0,'(objectclass=*)',attrsonly=True)
[('dc=stroeder,dc=de', {'description': [], 'labeledURI': [],
'objectClass': [], 'associatedDomain': [], 'dc': [], 'o': [], 'seeAlso':
[]})]

So it seems that it simply works.

Ciao, Michael.

Re: Apache DS ignores attrsonly

[Michael S. <mi...@st...>]

Thorsten Kampe wrote:
> [4]>>> connection.search_s('ou=system', ldap.SCOPE_SUBTREE, 
> filterstr='(cn=*)', attrlist = ['cn'], attrsonly = True)

Just a wild guess: Could you please try again with attrsonly=1. Note
that this API has its roots in Python 1.x times where there was no
Boolean True/False type. It would be worth handling that gracefully though.

Ciao, Michael.

Apache DS ignores attrsonly

[Thorsten K. <tho...@th...>]

[Python 2.6.2, python-ldap 2.3.8, Apache DS 1.5.4]

Hi,

not sure whether this is an Apache DS or Python-LDAP bug: Apache DS 
replies with values although I specifically request it not to:

[1]>>> import ldap
[2]>>> connection = ldap.initialize('ldap://')
[3]>>> connection.simple_bind_s('uid=admin,ou=system', 'secret')
[3]    (97, [])
[4]>>> connection.search_s('ou=system', ldap.SCOPE_SUBTREE, 
filterstr='(cn=*)', attrlist = ['cn'], attrsonly = True)
[4]
[('uid=admin,ou=system', {'cn': ['system administrator']}),
 ('cn=Administrators,ou=groups,ou=system', {'cn': ['Administrators']})]

But:
~/.ldaprc
BASE    ou=system
BINDDN  uid=admin,ou=system
URI     ldap://

thorsten@tkampe[~]> ldapsearch -x -w secret -LLL -A "(cn=*)" cn
dn: uid=admin,ou=system
cn:

dn: cn=Administrators,ou=groups,ou=system
cn:

The same query works (does not return values) if I query an Active 
Directory or eDirectory server.


Thorsten

version 2.3.8

[Larry k. <lar...@ex...>]

Hi ..
Triying to install python-ldap-2.3.8 using the EXE on a server (windows 
2000)  that has python 2.4.4 installed (or so the plone site tells me)

however it won't install and tells me that "python 2.4 required which 
was not found in the registry"

is there some registry setting and / or environment variable that I need 
to set for installation to run correctly
Thanks
Larry

Please consider the environment before printing this email.

Examiner Publications (Cork) Ltd
Directors:  G. A. Crosbie (Chairman), Thomas J. Murphy (Chief Executive), A.W. Dinan (Secretary), T.P. Crosbie. 
Registered In Dublin, Ireland. Registered number: 73385. Registered Office: City Quarter, Lapps Quay, Cork.

Egg news :-)

[Torsten K. <pyt...@tk...>]

Hi list,

it's been a while, but I finally managed to build some fresh
Python-LDAP 2.3.8 eggs. In particular:

- Win32 (Statically linked to OpenLDAP 2.4.16 and OpenSSL 0.9.8k, no
  further DLLs necessary.)
- MacOS X 10.3 through 10.5 (Statically linked to OpenLDAP 2.4.16 and
  dynamically bound to the Cyrus-SASL and OpenSSL libs that ship with
  OS X 10.5.7 - only tested on 10.5.7 Intel - testers welcome!!!)
- Linux x86 and x86_64 (aka amd64) (Built on Gentoo Linux, dynamically
  linked to OpenLDAP 2.4.16, Cyrus-SASL 2.1.23, OpenSSL 0.9.8k, all
  compiled with glibc-2.10.1)

All eggs are available for Python versions 2.4 through 2.6 and can be
downloaded via

	http://svn.kmrc.de/download/distribution/contrib/

@Michael: Can you please add the '/contrib/' subdir to the download
link on the webpage and replace the HTML snippet beginning with
"For the .egg files to work [...]" up to "[...] from the same directory
as the .egg files" by the one attached (provided you have no objections
to it, of course. ;-)

Best regards,
Torsten
-- 
Anyone can do any amount of work provided it isn't the work he is
supposed to be doing at the moment.
		-- Robert Benchley

Re: Egg news :-)

[Torsten K. <pyt...@tk...>]

Hi Michael,
 
> Please check http://www.python-ldap.org/download.shtml
> whether that's ok.

that's excellent!

Thanks for the fast reply.

Torsten
-- 
Fon: +49-7071-700240 | Fax: +49-7071-700241 | http://www.tk-webart.de

  The best cure for insomnia is to get a lot of sleep. -W.C. Fields

Re: Egg news :-)

[Michael S. <mi...@st...>]

Torsten Kurbad wrote:
> @Michael: Can you please

Please check http://www.python-ldap.org/download.shtml
whether that's ok.

Ciao, Michael.

Re: Egg news :-)

[Alberto L. <pl...@al...>]

Torsten,

That's excellent news for Windows users - the dll management was an extra
chore I am glad to get rid of! :-)

Congrats,

Alberto

On Tue, Jul 7, 2009 at 9:56 AM, Torsten Kurbad <pyt...@tk...>wrote:

> Hi list,
>
> it's been a while, but I finally managed to build some fresh
> Python-LDAP 2.3.8 eggs. In particular:
>
> - Win32 (Statically linked to OpenLDAP 2.4.16 and OpenSSL 0.9.8k, no
>  further DLLs necessary.)
> - MacOS X 10.3 through 10.5 (Statically linked to OpenLDAP 2.4.16 and
>  dynamically bound to the Cyrus-SASL and OpenSSL libs that ship with
>  OS X 10.5.7 - only tested on 10.5.7 Intel - testers welcome!!!)
> - Linux x86 and x86_64 (aka amd64) (Built on Gentoo Linux, dynamically
>  linked to OpenLDAP 2.4.16, Cyrus-SASL 2.1.23, OpenSSL 0.9.8k, all
>  compiled with glibc-2.10.1)
>
> All eggs are available for Python versions 2.4 through 2.6 and can be
> downloaded via
>
>        http://svn.kmrc.de/download/distribution/contrib/
>
> @Michael: Can you please add the '/contrib/' subdir to the download
> link on the webpage and replace the HTML snippet beginning with
> "For the .egg files to work [...]" up to "[...] from the same directory
> as the .egg files" by the following lines (provided you have no
> objections to them, of course. ;-)
>
> --- snip ---
>
> Prerequisites:
>
> <ul>
>  <li>
>    <b>for Linux:</b> OpenLDAP-2.4.16, OpenSSL-0.9.8k, and
>    Cyrus-SASL-2.1.23 must be properly installed on your system.
>  </li>
>  <li>
>    <b>for MacOS X:</b> The .egg files are statically linked to
>    OpenLDAP 2.4.16, but only tested on OS X 10.5.7 Intel.<br>
>    <b>Testers with 10.3 through 10.4 and/or PPC machines are
>    welcome!</b>
>  </li>
>  <li>
>    <b>for MS Windows:</b> The Windows eggs are statically linked to
>    all necessary libraries and should run out of the box.
>  </li>
> </ul>
>
> --- snap ---
>
> Btw.: Earlier today I sent the same mail to the list, but tried to send
> the snippet as an attachment. That didn't seem to work, probably due to
> SF list restrictions...
>
> Best regards,
> Torsten
> --
> Anyone can do any amount of work provided it isn't the work he is
> supposed to be doing at the moment.
>                -- Robert Benchley
>
>
> ------------------------------------------------------------------------------
> Enter the BlackBerry Developer Challenge
> This is your chance to win up to $100,000 in prizes! For a limited time,
> vendors submitting new applications to BlackBerry App World(TM) will have
> the opportunity to enter the BlackBerry Developer Challenge. See full prize
> details at: http://p.sf.net/sfu/blackberry
> _______________________________________________
> Python-LDAP-dev mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-ldap-dev
>

Egg news :-)

[Torsten K. <pyt...@tk...>]

Hi list,

it's been a while, but I finally managed to build some fresh
Python-LDAP 2.3.8 eggs. In particular:

- Win32 (Statically linked to OpenLDAP 2.4.16 and OpenSSL 0.9.8k, no
  further DLLs necessary.)
- MacOS X 10.3 through 10.5 (Statically linked to OpenLDAP 2.4.16 and
  dynamically bound to the Cyrus-SASL and OpenSSL libs that ship with
  OS X 10.5.7 - only tested on 10.5.7 Intel - testers welcome!!!)
- Linux x86 and x86_64 (aka amd64) (Built on Gentoo Linux, dynamically
  linked to OpenLDAP 2.4.16, Cyrus-SASL 2.1.23, OpenSSL 0.9.8k, all
  compiled with glibc-2.10.1)

All eggs are available for Python versions 2.4 through 2.6 and can be
downloaded via

	http://svn.kmrc.de/download/distribution/contrib/

@Michael: Can you please add the '/contrib/' subdir to the download
link on the webpage and replace the HTML snippet beginning with
"For the .egg files to work [...]" up to "[...] from the same directory
as the .egg files" by the following lines (provided you have no
objections to them, of course. ;-)

--- snip ---

Prerequisites:

<ul>
  <li>
    <b>for Linux:</b> OpenLDAP-2.4.16, OpenSSL-0.9.8k, and
    Cyrus-SASL-2.1.23 must be properly installed on your system.
  </li>
  <li>
    <b>for MacOS X:</b> The .egg files are statically linked to
    OpenLDAP 2.4.16, but only tested on OS X 10.5.7 Intel.<br>
    <b>Testers with 10.3 through 10.4 and/or PPC machines are
    welcome!</b>
  </li>
  <li>
    <b>for MS Windows:</b> The Windows eggs are statically linked to
    all necessary libraries and should run out of the box.
  </li>
</ul>

--- snap ---

Btw.: Earlier today I sent the same mail to the list, but tried to send
the snippet as an attachment. That didn't seem to work, probably due to
SF list restrictions...

Best regards,
Torsten
-- 
Anyone can do any amount of work provided it isn't the work he is
supposed to be doing at the moment.
		-- Robert Benchley

Re: server sort

[Michael S. <mi...@st...>]

Anil wrote:
> I am having a bit of a problem trying to setup the controlValue in 
> LDAPControl for doing server sorting. My LDAP server supports this 
> control, but I keep getting back Not supported error. Clearly this is a 
> problem on my end with how I am passing in controlValue.
> 
> I am not that familiar with BER encoding.
> 
> So, from what I've found, I tried doing something like this:
> 
> from pyasn1.type import univ, namedtype
> from pyasn1.codec.ber import encoder
> 
> seq = univ.Sequence(
> componentType=namedtype.NamedTypes(namedtype.NamedType('attributeType', 
> univ.OctetString("uid")))
> )
> 
> control = [ldap.controls.LDAPControl('1.2.840.113556.1.4.473',True,seq)]
> 
> 
> I then pass control to LDAPObject.search_ext().
> 
> That doesn't work, and I am sure I massacred my intepretation of using 
> the pyasn1 module. Unfortunately, the documentation for it is not clear 
> to me.

Never did this myself but here are some hints:

1. You have to actually encode the ASN.1 data structure represented in
pyasn1 as BER. So you would have to call pyasn1.codec.ber.encoder(seq)
somewhere.

2. You should more carefully read RFC 2891: SortKeyList is SEQUENCE OF
SEQUENCE { .. }. I don't see the nested SEQUENCE in your code snipped above.

3. The python-ldap way of implementing a LDAP control would be deriving
a new class for this control and implement the methods
encodeControlValue() and decodeControlValue() as needed.

Ciao, Michael.

server sort

[Anil <an...@en...>]

I am having a bit of a problem trying to setup the controlValue in 
LDAPControl for doing server sorting. My LDAP server supports this 
control, but I keep getting back Not supported error. Clearly this is a 
problem on my end with how I am passing in controlValue.

I am not that familiar with BER encoding.

So, from what I've found, I tried doing something like this:

from pyasn1.type import univ, namedtype
from pyasn1.codec.ber import encoder

seq = univ.Sequence(
componentType=namedtype.NamedTypes(namedtype.NamedType('attributeType', 
univ.OctetString("uid")))
)

control = [ldap.controls.LDAPControl('1.2.840.113556.1.4.473',True,seq)]


I then pass control to LDAPObject.search_ext().

That doesn't work, and I am sure I massacred my intepretation of using 
the pyasn1 module. Unfortunately, the documentation for it is not clear 
to me.

Any tips?

Thanks