openldap-bugs

openldap-bugs@openldap.org

1 participants
20996 discussions

(ITS#5031) Question about transaction in OpenLDAP
by lixin922＠huawei.com 28 Jun '07

28 Jun '07

Full_Name: lixin Version: OpenLDAP2.4.4alpha OS: Linux URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (210.21.230.126) Hello, I have known that the OpenLDAP2.4 will support transaction from roadmap.Now I am testing OpenLDAP2.4.4alpha,But I am not sure whether this version suports transation.If it supports how to use it.If not,about which version will support it,and when this version will appear. Thank you very much.

1 0

(ITS#5030) Setting/knowing max query size
by bruno_haleblian＠carrefour.com 27 Jun '07

27 Jun '07

Full_Name: Bruno Version: 2.3.21 OS: redhat AS 3 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (217.77.224.130) Hi, I am looking for a way to limit ldap query size - there may be one in slapd.conf but I could not find it yet(still reading). Sometimes slapd process crashes because of malformed - too lenghty requests. While this is due to a buggy EAI updater which will be fixed - I still think it should be safer to limit this size from server side. thanks

1 0

Re: (ITS#5028) incomplete slapcat docs
by ghenry＠suretecsystems.com 26 Jun '07

26 Jun '07

<quote who="h.b.furuseth(a)usit.uio.no"> > hyc(a)symas.com writes: >> steve(a)stevenwills.com wrote: >>> The slapcat man page says in the Limitations section: >>> >>> In general, your slapd(8) should not be running (at least, not >>> in >>> read-write mode) when you do this to ensure consistency of the >>> database. >>> (...) >> Given that back-ldbm has been deleted for 2.4, I guess we can just >> delete this sentence. > > It could produce garbage data with back-ldif, and with some foreign > database module. I think it should say it's safe with bdb (and null). > Could copy it to the slapd-bdb(5) too. (I don't suggest to make > slapcat(8) refer the user to that, since there is only one example > anyway.) Obviously hdb too. Would it produce garbage on 2.4? > > -- > Regards, > Hallvard > > >

1 0

Re: (ITS#5028) incomplete slapcat docs
by ghenry＠suretecsystems.com 26 Jun '07

26 Jun '07

<quote who="hyc(a)symas.com"> > steve(a)stevenwills.com wrote: >> Full_Name: Steve Wills >> Version: 2.3.19 >> OS: Fedora >> URL: ftp://ftp.openldap.org/incoming/ >> Submission from: (NULL) (65.15.231.202) >> >> >> The slapcat man page says in the Limitations section: >> >> In general, your slapd(8) should not be running (at least, not in >> read-write mode) when you do this to ensure consistency of the database. >> >> However, I've been told several times that this only applies to ldbm and >> not >> bdb. Not sure about other types, but it would be good to clarify this >> section. >> > Given that back-ldbm has been deleted for 2.4, I guess we can just delete > this > sentence. I would agree. > -- > -- Howard Chu > Chief Architect, Symas Corp. http://www.symas.com > Director, Highland Sun http://highlandsun.com/hyc/ > Chief Architect, OpenLDAP http://www.openldap.org/project/ > > >

1 0

Re: (ITS#5028) incomplete slapcat docs
by h.b.furuseth＠usit.uio.no 26 Jun '07

26 Jun '07

hyc(a)symas.com writes: > steve(a)stevenwills.com wrote: >> The slapcat man page says in the Limitations section: >> >> In general, your slapd(8) should not be running (at least, not in >> read-write mode) when you do this to ensure consistency of the database. >> (...) > Given that back-ldbm has been deleted for 2.4, I guess we can just > delete this sentence. It could produce garbage data with back-ldif, and with some foreign database module. I think it should say it's safe with bdb (and null). Could copy it to the slapd-bdb(5) too. (I don't suggest to make slapcat(8) refer the user to that, since there is only one example anyway.) -- Regards, Hallvard

1 0

Re: (ITS#5029) refint schema unavailable
by hyc＠symas.com 26 Jun '07

26 Jun '07

dirk.a.schaefer(a)bluewin.ch wrote: > Full_Name: Dirk Alexander Scheafer > Version: openldap-2.3.35-r1 > OS: gentoo 2007.0 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (213.3.4.29) > > > i have all my openldap configuration within it's internal cn=config db, > slapd.conf has been removed. i use several overlays where refint is one of them. > after slapd has started, the refint specific attributes and objectclass are not > available, not visible within the schema. > > by this, the refint overlay is not usable for my installation but there is no > error shown anywhere, regardless at which debug/log level the server is beeing > executed. This is a known limitation in 2.3, fixed in 2.4. In fact this condition is logged both to stderr and to syslog: config_build_entry: "olcDatabase={1}bdb" WARNING: No dynamic config support for overlay refint. config_build_entry: "olcOverlay={0}refint" config_build_entry: "olcDatabase={2}monitor" This ITS will be closed. -- -- Howard Chu Chief Architect, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

feature --enable-ppolicy
by Philippe Radix 26 Jun '07

26 Jun '07

hello I try to test the new feature the new version openldap (openldap-2.3.36) cd /alcatel/PR/ tar xvzf openldap-2.3.36.tgz cd /alcatel/PR/openldap-2.3.36 ./configure --prefix=/opt/ldap/OpenLDAP --with-cyrus-sasl --with-tls --enable-backends --enable-overlays make depend make make install i create slapd.cond --------------- vi slapd.conf include /opt/ldap/OpenLDAP/etc/openldap/schema/core.schema include /opt/ldap/OpenLDAP/etc/openldap/schema/ppolicy.schema include /opt/ldap/OpenLDAP/etc/openldap/schema/cosine.schema include /opt/ldap/OpenLDAP/etc/openldap/schema/inetorgperson.schema overlay ppolicy ppolicy_default "cn=StandardPolicy,ou=Policies,dc=alcatel,dc=com" ppolicy_use_lockout pidfile /alcatel/openldapTest/slapd.pid argsfile /alcatel/openldapTest/slapd.args database bdb suffix "dc=alcatel,dc=com" rootdn "cn=Admin,dc=alcatel,dc=com" directory /alcatel/openldapTest/data by self write by anonymous auth by * none access to * by self write by anonymous auth by * read i create defaultpolicy ------------------ dn: ou=Policies,dc=alcatel,dc=com objectClass: top objectClass: organizationalUnit ou: Policies structuralObjectClass: organizationalUnit dn: cn=StandardPolicy,ou=Policies,dc=alcatel,dc=com objectClass: top objectClass: device objectClass: pwdPolicy cn: StandardPolicy pwdAttribute: userPassword pwdLockoutDuration: 120 pwdInHistory: 5 pwdCheckQuality: 2 pwdExpireWarning: 86400 pwdMaxAge: 864000 pwdMinLength: 5 pwdGraceAuthNLimit: 5 pwdAllowUserChange: TRUE pwdMustChange: FALSE pwdMaxFailure: 3 pwdFailureCountInterval: 120 pwdSafeModify: FALSE structuralObjectClass: device i create user ------------ dn:cn=prtest,dc=alcatel,dc=com sn: prtest userpassword: prtest objectClass: person pwdPolicySubentry: cn=StandardPolicy cn: prtest i thinl all are ok for the policies features but and i run server ldap -------------- and i want to change password with a bad policy password ldappasswd -h 192.200.244.87 -p 389 -x -D cn=prtest,dc=alcatel,dc=com -w prtest -s titi -e ppolicy i have Result: Success (0) as answer i dont arive to see the policyies error with client ldap could you help me regards -- ************************************************************ Philippe Radix Alcatel CIT (philippe.radix(a)alcatel-lucent.fr) Tel.: (33) 01 3077 2829

2 1

Re: (ITS#5028) incomplete slapcat docs
by hyc＠symas.com 26 Jun '07

26 Jun '07

steve(a)stevenwills.com wrote: > Full_Name: Steve Wills > Version: 2.3.19 > OS: Fedora > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (65.15.231.202) > > > The slapcat man page says in the Limitations section: > > In general, your slapd(8) should not be running (at least, not in > read-write mode) when you do this to ensure consistency of the database. > > However, I've been told several times that this only applies to ldbm and not > bdb. Not sure about other types, but it would be good to clarify this section. > Given that back-ldbm has been deleted for 2.4, I guess we can just delete this sentence. -- -- Howard Chu Chief Architect, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

(ITS#5029) refint schema unavailable
by dirk.a.schaefer＠bluewin.ch 25 Jun '07

25 Jun '07

Full_Name: Dirk Alexander Scheafer Version: openldap-2.3.35-r1 OS: gentoo 2007.0 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (213.3.4.29) i have all my openldap configuration within it's internal cn=config db, slapd.conf has been removed. i use several overlays where refint is one of them. after slapd has started, the refint specific attributes and objectclass are not available, not visible within the schema. by this, the refint overlay is not usable for my installation but there is no error shown anywhere, regardless at which debug/log level the server is beeing executed. greez d. a. schaefer

1 0

(ITS#5028) incomplete slapcat docs
by steve＠stevenwills.com 25 Jun '07

25 Jun '07

Full_Name: Steve Wills Version: 2.3.19 OS: Fedora URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (65.15.231.202) The slapcat man page says in the Limitations section: In general, your slapd(8) should not be running (at least, not in read-write mode) when you do this to ensure consistency of the database. However, I've been told several times that this only applies to ldbm and not bdb. Not sure about other types, but it would be good to clarify this section.

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs