Re: Problem with names that include ","

Hello ! Thanks for your reply and that of Marc Balmer. But I still wonder if it is allowed by LDAP or LDIF- Specification to have a comma in dn. I also tried it with "" and Base64, some of which openldap accepted. C. Holtermann Yves Dorfsman schrieb: > Christoph Holtermann wrote: > > >> I am

Re: Problem with names that include ","

Hi ! >> >> Thanks for your reply and that of Marc Balmer. >> But I still wonder if it is allowed by LDAP or LDIF- >> Specification to have a comma in dn. I also tried it >> with "" and Base64, some of which >> openldap accepted. > > take a look at RFC 1779. A semicolon could be used as an > altern

Re: Problem with names that include ","

Am 02.06.2009 um 13:13 schrieb Christoph Holtermann: > Hello ! > > Thanks for your reply and that of Marc Balmer. > But I still wonder if it is allowed by LDAP or LDIF- > Specification to have a comma in dn. I also tried it > with "" and Base64, some of which > openldap accepted. take a look at

Re: Problem with names that include ","

Christoph Holtermann wrote: > I just fed it with > > dn: cn="Lehmann, Veronika",dc=Adressbuch,dc=christoph > objectclass: top > objectclass: person > objectclass: inetOrgPerson > objectclass: mozillaAbPersonAlpha > sn: Lehmann > cn: Lehmann, Veronika And that's the correct LDIF for the entry you

Re: Problem with names that include ","

Marc Balmer wrote: > take a look at RFC 1779. A semicolon could be used as an > alternate delimiter and it shuld be possible to enclose strings > in quotes, i.e. like this: RFC 1779 was part of LDAPv2 standard which has been obsoleted for quite a while now. Today RFC 4514 is relevant for LDAPv3-b

Re: Problem with names that include ","

Michael Ströder wrote: > Christoph Holtermann wrote: >> I just fed it with >> >> dn: cn="Lehmann, Veronika",dc=Adressbuch,dc=christoph >> objectclass: top >> objectclass: person >> objectclass: inetOrgPerson >> objectclass: mozillaAbPersonAlpha >> sn: Lehmann >> cn: Lehmann, Veronika > > And that'

Re: Problem with names that include ","

Hello ! Still working on commas in dn. When I now look at the functions supplied in python ldap there is for example : >>> a='cn="lehmann, Andreas",dc=Adressbuch' >>> b=ldap.dn.str2dn(a) >>> b [[('cn', 'lehmann, Andreas', 1)], [('dc', 'Adressbuch', 1)]] >>> ldap.dn.dn2str(b) 'cn=lehmann\\, Andrea

Re: Problem with names that include ","

Yves Dorfsman wrote: > Christoph Holtermann wrote: > >> I am working on a filter that makes Thunderbirds LDIF-Output >> importable to OpenLDAP. It works quite fine except for names >> that include ",". OpenLDAP dislikes the output that is produced >> like : >> >> dn: cn=Lehmann\, Veronika,dc=Adres

Re: Problem with names that include ","

Christoph Holtermann wrote: > > Still working on commas in dn. When I now look > at the functions supplied in python ldap there is > for example : > a='cn="lehmann, Andreas",dc=Adressbuch' b=ldap.dn.str2dn(a) b > [[('cn', 'lehmann, Andreas', 1)], [('dc', 'Adressbuch', 1)]] lda

Re: Problem with names that include ","

Michael Ströder wrote: >> >>> I am working on a filter that makes Thunderbirds LDIF-Output >>> importable to OpenLDAP. It works quite fine except for names >>> that include ",". OpenLDAP dislikes the output that is produced >>> like : >>> >>> dn: cn=Lehmann\, Veronika,dc=Adressbuch,dc=christoph >>

Re: Problem with names that include ","

Am 02.06.2009 um 14:12 schrieb Michael Ströder: > Marc Balmer wrote: >> take a look at RFC 1779. A semicolon could be used as an >> alternate delimiter and it shuld be possible to enclose strings >> in quotes, i.e. like this: > > RFC 1779 was part of LDAPv2 standard which has been obsoleted for

Re: Problem with names that include ","

Christoph Holtermann wrote: > I am working on a filter that makes Thunderbirds LDIF-Output > importable to OpenLDAP. It works quite fine except for names > that include ",". OpenLDAP dislikes the output that is produced > like : Can you please elaborate on which exact problems you have with OpenLD

Re: problem with set_option and tls

Michael Ströder wrote: Mike Lovell wrote: Michael Ströder wrote: I guess you're using python-ldap built against OpenLDAP 2.3 client libs. With OpenLDAP 2.4 connection-specific TLS options should be supported. I am using a machine with Ubuntu 9.04 which has the 2.4 OpenLDAP l

Python-ldap and client-only OpenLDAP

Hey everyone, I want to build OpenLDAP and Python-LDAP from source. However, I can't install Berkeley DB so I installed Open-LDAP with ./configure --disable-slapd --disable-slurpd I then built and installed Python-LDAP. However, when I try to import, I get File "/usr/local/lib/python2.6/site-

Re: Python-ldap and client-only OpenLDAP

Guillaume Simard wrote: > > I want to build OpenLDAP and Python-LDAP from source. > However, I can't install Berkeley DB so I installed Open-LDAP with > > ./configure --disable-slapd --disable-slurpd Yes, that should be sufficient for python-ldap. > I then built and installed Python-LDAP. > >