openldap-bugs

openldap-bugs@openldap.org

1 participants
20966 discussions

Re: (ITS#6986) conversion to run-time configuration (RTC) for slapo-constraint
by masarati＠aero.polimi.it 06 Jul '11

06 Jul '11

There are clearly two bugs: "count" misses the number (same for "size") and the prefix "restrict=" is repeated. Fixed in master, please test and report. p. > --On Tuesday, July 05, 2011 9:22 PM +0000 florian.dufner(a)uni-ulm.de wrote: > >> Full_Name: Florian Dufner >> Version: 2.4.26 >> OS: SunOS sun 5.10 i86pc >> URL: >> Submission from: (NULL) (91.16.117.246) >> >> >> Conversion to run-time configuration (RTC) does not work with every >> configuration option of slapo-constraint. >> >> Problem #1: (count constraints) >> constraint_attribute mail count 1 >> is converted to >> olcConstraintAttribute:: bWFpbCBjb3VudCA= > > This is base-64 encoded, not garbage. I suggest you base-64 decode it to > see the actual value. > >> The attribute is garbled after conversion. slapd will not run until this >> is fixed. >> >> Problem #2: (restrict parameter) >> constraint_attribute mail regex ^[[:alnum:].-]+@host$ >> restrict="ldap:///ou=people,dc=host??sub?(objectClass=posixAccount)" >> is converted to >> olcConstraintAttribute: mail regex ^[[:alnum:].-]+@host$ restr >> ict="restrict=ldap:///ou=people,dc=host??sub?(obj >> ectClass=posixAccount)" >> >> The complete restrict parameter from the old configuration format >> (including "restrict=") is appended after a "restrict=". >> slapd will not run until this is fixed. >> > > This sounds valid. > > --Quanah > > -- > > Quanah Gibson-Mount > Sr. Member of Technical Staff > Zimbra, Inc > A Division of VMware, Inc. > -------------------- > Zimbra :: the leader in open source messaging and collaboration > > >

1 0

Re: (ITS#6986) conversion to run-time configuration (RTC) for slapo-constraint
by florian.dufner＠uni-ulm.de 06 Jul '11

06 Jul '11

Am 07.07.2011 04:12, schrieb Quanah Gibson-Mount: >> Problem #1: (count constraints) >> constraint_attribute mail count 1 >> is converted to >> olcConstraintAttribute:: bWFpbCBjb3VudCA= > > This is base-64 encoded, not garbage. I suggest you base-64 decode it > to see the actual value. Okay, base-64 decoded it is "mail count". But as I wrote: >> The attribute is garbled after conversion. slapd will not run until this >> is fixed. So the problem is that the number after count is not included in conversion. After adding " <number>" slapd will start. Is there a specific mechanism for the decision of what attributes get base64-encoded in conversion? In case of the count type constraint I can't see why it's needed. FloD.

1 0

Re: (ITS#6986) conversion to run-time configuration (RTC) for slapo-constraint
by quanah＠zimbra.com 06 Jul '11

06 Jul '11

--On Tuesday, July 05, 2011 9:22 PM +0000 florian.dufner(a)uni-ulm.de wrote: > Full_Name: Florian Dufner > Version: 2.4.26 > OS: SunOS sun 5.10 i86pc > URL: > Submission from: (NULL) (91.16.117.246) > > > Conversion to run-time configuration (RTC) does not work with every > configuration option of slapo-constraint. > > Problem #1: (count constraints) > constraint_attribute mail count 1 > is converted to > olcConstraintAttribute:: bWFpbCBjb3VudCA= This is base-64 encoded, not garbage. I suggest you base-64 decode it to see the actual value. > The attribute is garbled after conversion. slapd will not run until this > is fixed. > > Problem #2: (restrict parameter) > constraint_attribute mail regex ^[[:alnum:].-]+@host$ > restrict="ldap:///ou=people,dc=host??sub?(objectClass=posixAccount)" > is converted to > olcConstraintAttribute: mail regex ^[[:alnum:].-]+@host$ restr > ict="restrict=ldap:///ou=people,dc=host??sub?(obj > ectClass=posixAccount)" > > The complete restrict parameter from the old configuration format > (including "restrict=") is appended after a "restrict=". > slapd will not run until this is fixed. > This sounds valid. --Quanah -- Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

(ITS#6986) conversion to run-time configuration (RTC) for slapo-constraint
by florian.dufner＠uni-ulm.de 05 Jul '11

05 Jul '11

Full_Name: Florian Dufner Version: 2.4.26 OS: SunOS sun 5.10 i86pc URL: Submission from: (NULL) (91.16.117.246) Conversion to run-time configuration (RTC) does not work with every configuration option of slapo-constraint. Problem #1: (count constraints) constraint_attribute mail count 1 is converted to olcConstraintAttribute:: bWFpbCBjb3VudCA= The attribute is garbled after conversion. slapd will not run until this is fixed. Problem #2: (restrict parameter) constraint_attribute mail regex ^[[:alnum:].-]+@host$ restrict="ldap:///ou=people,dc=host??sub?(objectClass=posixAccount)" is converted to olcConstraintAttribute: mail regex ^[[:alnum:].-]+@host$ restr ict="restrict=ldap:///ou=people,dc=host??sub?(obj ectClass=posixAccount)" The complete restrict parameter from the old configuration format (including "restrict=") is appended after a "restrict=". slapd will not run until this is fixed.

1 0

RE: (ITS#6985) sssvlv / greaterThanOrEqual problem
by ctcard＠hotmail.com 05 Jul '11

05 Jul '11

> > > > I am running slapd built from HEAD on June 30th 2011, with back-sql > > Can you confirm this issue with another backend, e.g. back-bdb? Bugs > specific to back-sql or to interaction with it could receive only marginal > attention. > > p. > I've imported my data into a server with a bdb backend, and I see the same problem. Looking at the code in sssvlv.c, it uses tavl_find3() to search the values, but the code in tavl_find3() looks to me that it only works properly with an exact match type of matching rule: Avlnode * tavl_find3( Avlnode *root, const void *data, AVL_CMP fcmp, int *ret ) { int cmp = -1, dir; Avlnode *prev = root; while ( root != 0 && (cmp = (*fcmp)( data, root->avl_data )) != 0 ) { prev = root; dir = cmp > 0; root = avl_child( root, dir ); } *ret = cmp; return root ? root : prev; } since the while loop terminates when the fcmp function returns 0 (i.e. exact match). Chris

1 0

Re: (ITS#6985) sssvlv / greaterThanOrEqual problem
by masarati＠aero.polimi.it 05 Jul '11

05 Jul '11

> Full_Name: Chris Card > Version: HEAD (on 30 June 2011) > OS: Centos 5.4 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (91.194.158.133) > > > I am running slapd built from HEAD on June 30th 2011, with back-sql Can you confirm this issue with another backend, e.g. back-bdb? Bugs specific to back-sql or to interaction with it could receive only marginal attention. p. > backend, and > pcache and sssvlv overlays. > > I am submitting a search request with vlv and sort controls. > > In the sort control I am specifying attributeType cn and orderingRule > caseIgnoreOrderingMatch. > > If I specify 'd' as the greaterThanOrEqual value of the vlv control, > beforeCount > 0 and afterCount 4, I get 5 entries with the following cns returned: > > Dave Smith > Fiona Smith > Glynis Smith > Jane Smith > Jennifer Smith > > If I specify 'g' in greaterThanOrEqual I get: > > Glynis Smith > Jane Smith > Jennifer Smith > Jim Smith > Mark Smith > > But if I specify 'f' I get no entries returned. > >

1 0

(ITS#6985) sssvlv / greaterThanOrEqual problem
by ctcard＠hotmail.com 05 Jul '11

05 Jul '11

Full_Name: Chris Card Version: HEAD (on 30 June 2011) OS: Centos 5.4 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (91.194.158.133) I am running slapd built from HEAD on June 30th 2011, with back-sql backend, and pcache and sssvlv overlays. I am submitting a search request with vlv and sort controls. In the sort control I am specifying attributeType cn and orderingRule caseIgnoreOrderingMatch. If I specify 'd' as the greaterThanOrEqual value of the vlv control, beforeCount 0 and afterCount 4, I get 5 entries with the following cns returned: Dave Smith Fiona Smith Glynis Smith Jane Smith Jennifer Smith If I specify 'g' in greaterThanOrEqual I get: Glynis Smith Jane Smith Jennifer Smith Jim Smith Mark Smith But if I specify 'f' I get no entries returned.

1 0

Re: (ITS#6984) Enable draft-wahl-ldap-session in RE24
by masarati＠aero.polimi.it 04 Jul '11

04 Jul '11

> Full_Name: Michael Ströder > Version: 2.4.x > OS: > URL: > Submission from: (NULL) (84.128.228.27) > > > It seems there is support for draft-wahl-ldap-session in OpenLDAP's source > since > 2007 but it seems not to be enabled in a default build. It's hidden behind > ifdef-statements and one has to use -DLDAP_DEVEL when compiling which is > not > supposed to work with RE24. > > I've tested it with HEAD and I'd be glad this could be enabled for > standard > builds in 2.4 series. As far as I understand, support is complete and conforms to draft as of the time it was implemented. Since the draft expired, it has never been released. Moreover, I sent the author some comments about how the draft could be improved, IMHO, but received no answer (I don't recall whether the discussion was in ldapext or personal, though). If it can be useful, I surely favour its release, provided this complies with the project's policy towards support for expired drafts. p.

1 0

(ITS#6984) Enable draft-wahl-ldap-session in RE24
by michael＠stroeder.com 04 Jul '11

04 Jul '11

Full_Name: Michael Ströder Version: 2.4.x OS: URL: Submission from: (NULL) (84.128.228.27) It seems there is support for draft-wahl-ldap-session in OpenLDAP's source since 2007 but it seems not to be enabled in a default build. It's hidden behind ifdef-statements and one has to use -DLDAP_DEVEL when compiling which is not supposed to work with RE24. I've tested it with HEAD and I'd be glad this could be enabled for standard builds in 2.4 series. Ciao, Michael.

1 0

(ITS#6983) modrdn operations on hdb databases create duplicate return results
by quanah＠zimbra.com 02 Jul '11

02 Jul '11

Full_Name: Quanah Gibson-Mount Version: 2.4.25 OS: Linux 2.6 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (75.111.45.108) When a modrdn operation is done on a subtree (I.e., subtree rename), the result is that back-hdb will return certain entries in that subtree multiple times. Stopping and restarting slapd fixes the behavior. Example: ldapsearch -x -v -H 'ldap://HOST ' -w PASSWORD -D 'uid=zimbra,cn=admins,cn=zimbra' -b "dc=NEWDOMAIN,dc=COM" ldap_initialize( ldap://HOST:389/??base ) filter: (objectclass=*) requesting: All userApplication attributes # extended LDIF # # LDAPv3 # base <dc=NEWDOMAIN,dc=COM> with scope subtree # filter: (objectclass=*) # requesting: ALL # # d-fashion.be dn: dc=NEWDOMAIN,dc=COM o: NEWDOMAIN.com domain zimbraDomainName: NEWDOMAIN.COM zimbraDomainStatus: active zimbraPublicServiceHostname: mail.domain.com zimbraId: affb06b8-79bc-430a-adf7-411cc45e8f00 zimbraMailStatus: enabled objectClass: dcObject objectClass: organization objectClass: zimbraDomain zimbraDomainType: local dc: NEWDOMAIN zimbraPreAuthKey: PRIVATE # people, NEWDOMAIN.COM dn: ou=people,dc=NEWDOMAIN,dc=COM ou: people objectClass: organizationalRole cn: people # people, NEWDOMAIN.COM dn: ou=people,dc=NEWDOMAIN,dc=COM ou: people objectClass: organizationalRole cn: people

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