openldap-bugs

openldap-bugs@openldap.org

1 participants
20963 discussions

(ITS#8287) ldap server address book
by ikshafi＠yahoo.com 22 Oct '15

22 Oct '15

Full_Name: sifat ara nil Version: 2.4.39 OS: centros URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (103.230.63.94) I have create a Ldap server for Email address book purpose .Its running well and i am able to search by name . But it's not showing all address in microsoft outlook address book without search . how can i make it visible .

1 0

(ITS#8286) Add missing matching rule for olcMirrorMode
by quanah＠openldap.org 21 Oct '15

21 Oct '15

Full_Name: Quanah Gibson-Mount Version: RE24 OS: Linux 2.6 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (75.111.52.177) The olcMirrorMode attribute in cn=config is missing an EQUALITY matching rule, which breaks the ability to use it for ldapcompare and other operations. That should be fixed.

1 0

Re: (ITS#8285) RFE slapo-ppolicy: fall back to createTimestamp
by hyc＠symas.com 21 Oct '15

21 Oct '15

michael(a)stroeder.com wrote: > Full_Name: Michael Str.der > Version: > OS: > URL: > Submission from: (NULL) (213.240.180.113) > > > If pwdMaxAge is set in a pwdPolicy entry but the user's entry does not contain > pwdChangedTime attribute createTimestamp should be used instead to determine > whether password is expired or not. > > The case above can happen if there are already existing entries with > userPassword and slapo-ppolicy gets installed and activated later. > No. The spec says for pwdChangedTime "If this attribute does not exist, the password will never expire." Closing this ITS. -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

(ITS#8285) RFE slapo-ppolicy: fall back to createTimestamp
by michael＠stroeder.com 21 Oct '15

21 Oct '15

Full_Name: Michael Str.der Version: OS: URL: Submission from: (NULL) (213.240.180.113) If pwdMaxAge is set in a pwdPolicy entry but the user's entry does not contain pwdChangedTime attribute createTimestamp should be used instead to determine whether password is expired or not. The case above can happen if there are already existing entries with userPassword and slapo-ppolicy gets installed and activated later.

1 0

Re: (ITS#8284) back-relay: olcRelay issues with values containing white spaces
by michael＠stroeder.com 21 Oct '15

21 Oct '15

hyc(a)symas.com wrote: >> To reproduce the problem just configure back_relay with a value containing white >> spaces >> (i.e. olcRelay: ou=Dipartimento di Fisica,o=Università degli Studi di >> Milano,c=IT) > > Use double-quotes around arguments containing whitespace. Attribute 'olcRelay' is of LDAP syntax Distinguished Name (1.3.6.1.4.1.1466.115.121.1.12). So your statement is pretty surprising. > Closing this ITS. Really? Ciao, Michael.

1 0

Re: (ITS#8284) back-relay: olcRelay issues with values containing white spaces
by michele.bensi＠fisica.unimi.it 21 Oct '15

21 Oct '15

Well this was the first thing I tried, but when I use olcRelay: "ou=Dipartimento di Fisica,o=Università degli Studi di Milano,c=IT" I got ldap_add: Invalid syntax (21) additional info: olcRelay: value #0 invalid per syntax Then I tried with olcRelay: ou="Dipartimento di Fisica",o="Università degli Studi di Milano",c=IT I had the same error of extra cruft. I solved patching servers/slapd/back-relay/init.c this way --- a/servers/slapd/back-relay/init.c 2015-10-20 15:22:20.511667130 +0200 +++ b/servers/slapd/back-relay/init.c 2015-10-21 10:27:02.649251347 +0200 @@ -32,7 +32,7 @@ static ConfigTable relaycfg[] = { { "relay", "relay", 2, 2, 0, - ARG_MAGIC|ARG_DN, + ARG_MAGIC|ARG_DN|ARG_QUOTE, relay_back_cf, "( OLcfgDbAt:5.1 " "NAME 'olcRelay' " "DESC 'Relay DN' " On Wed, Oct 21, 2015 at 03:12:14PM +0100, Howard Chu wrote: > michele.bensi(a)fisica.unimi.it wrote: > >Full_Name: Michele Bensi > >Version: 2.4.42 > >OS: Linux > >URL: ftp://ftp.openldap.org/incoming/ > >Submission from: (NULL) (159.149.47.246) > > > > > >When configuring realy backend using a relay suffix containg spaces I got this > >error: > > > >ldap_add: Constraint violation (19) > > additional info: <olcRelay> extra cruft after <relay> > >A%A > >To reproduce the problem just configure back_relay with a value containing white > >spaces > >(i.e. olcRelay: ou=Dipartimento di Fisica,o=Università degli Studi di > >Milano,c=IT) > > Use double-quotes around arguments containing whitespace. > > Closing this ITS. > > -- > -- Howard Chu > CTO, Symas Corp. http://www.symas.com > Director, Highland Sun http://highlandsun.com/hyc/ > Chief Architect, OpenLDAP http://www.openldap.org/project/ -- Michele Bensi Unità Calcolo Dipartimento di Fisica Università degli Studi di Milano Via Celoria, 16 20133 Milano (MI) ITALY Phone: +39 02503 17341 Fax: +39 02503 17280 Room: I/T/4 "Unix is user-friendly. It's just very selective about who its friends are."

1 0

Re: (ITS#8284) back-relay: olcRelay issues with values containing white spaces
by hyc＠symas.com 21 Oct '15

21 Oct '15

michele.bensi(a)fisica.unimi.it wrote: > Full_Name: Michele Bensi > Version: 2.4.42 > OS: Linux > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (159.149.47.246) > > > When configuring realy backend using a relay suffix containg spaces I got this > error: > > ldap_add: Constraint violation (19) > additional info: <olcRelay> extra cruft after <relay> > A%A > To reproduce the problem just configure back_relay with a value containing white > spaces > (i.e. olcRelay: ou=Dipartimento di Fisica,o=Università degli Studi di > Milano,c=IT) Use double-quotes around arguments containing whitespace. Closing this ITS. -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

(ITS#8284) back-relay: olcRelay issues with values containing white spaces
by michele.bensi＠fisica.unimi.it 21 Oct '15

21 Oct '15

Full_Name: Michele Bensi Version: 2.4.42 OS: Linux URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (159.149.47.246) When configuring realy backend using a relay suffix containg spaces I got this error: ldap_add: Constraint violation (19) additional info: <olcRelay> extra cruft after <relay> A%A To reproduce the problem just configure back_relay with a value containing white spaces (i.e. olcRelay: ou=Dipartimento di Fisica,o=Università degli Studi di Milano,c=IT)

1 0

(ITS#8283) Incomplete documentation
by hadmut＠danisch.de 21 Oct '15

21 Oct '15

Full_Name: Hadmut Danisch Version: 2.4 OS: Linux URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (195.145.25.4) Hi, the openssl docs as http://www.openldap.org/doc/admin24/access-control.html describe the syntax of access rules in detail, but not as much about semantics. There is an access right "manage", but no description about what this is good for beyond reading and writing. According to Google, noone has ever asked, what this is good for. regards

1 0

(ITS#8282) WEB: Devel/tools page is out of date
by hyc＠openldap.org 20 Oct '15

20 Oct '15

Full_Name: Howard Chu Version: OS: URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (78.155.231.14) Submitted by: hyc http://www.openldap.org/devel/tools.html Still points to BerkeleyDB at www.sleepycat.com - this whole section should probably just be deleted now. I was looking on this page because I was wondering if we listed the Windows build tools. We should probably add links for MSYS/MinGW/MinGW64. I don't think anyone has used ePerl in ages. We haven't been on FreeBSD for a couple of years now. We haven't been using sendmail for years.

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