went on vacation, sorry for the delay.
If i modify/create (master) an userPassword its not replicated/sync in
the slave server.
After some tests and debugs (and reading) it worked...
in slapd.conf (slave) changed the acl order
access to * before access to attrs=userPassword
About the Oldap
Am Dienstag, 18. April 2006 02:43 schrieb Kurt D. Zeilenga:
At 12:27 AM 4/17/2006, Dr. Harry Knitter wrote:
Am Donnerstag, 13. April 2006 17:13 schrieb Lise Didillon:
At 08:39 13/04/06 +0200, Dr. Harry Knitter wrote:
Hello,
I am new with Openldap and with this list, too.
My problem
On Fri, Apr 14, 2006 at 12:57:08PM +0400, Dmitriy Kirhlarov wrote:
Timur Izhbulatov writes:
I'm running openldap-2.3.20 from FreeBSD 6.1-prerelease ports. The
slapd server is configured to run my backend shell script. But the
server fails to parse my output.
(...)
The slapd log looks
Greetings,
I have started looking into slurpd for server replication. We have a
small database, about 65000 entries, and want it to be available all of
the time.
I am going to put 2 different servers into two different locations, and
they need to be mirrors of each other. It looks like slurpd is
Jennifer Abel wrote:
Greetings,
I have started looking into slurpd for server replication. We have a
small database, about 65000 entries, and want it to be available all of
the time.
I am going to put 2 different servers into two different locations, and
they need to be mirrors of each other.
Jennifer Abel wrote:
Greetings,
I have started looking into slurpd for server replication.
We have a
small database, about 65000 entries, and want it to be
available all
of the time.
I am going to put 2 different servers into two different locations,
and they need to be
Dmitriy Kirhlarov writes:
We find problem. Return code must be LAST string in backend output
Yes. As 'man slapd-shell' says: The search RESULT should be preceded
by the entries in LDIF format, each entry followed by a blank line.
Maybe that needs to be clarified - if so, what should it say?
I don't know what versions of OpenLDAP are affected, but ITS 4323 snagged
me in a very similar situation for several revisions of OL 2.3.1x.
From the looks of things at
http://www.openldap.org/devel/cvsweb.cgi/servers/slapd/backglue.c?hideattic=1sortbydate=0
the problem was patched before the
We have a number of ACLs, in production on OpenLDAP 2.2.26, which are of
the form:
by set=user/eduPersonAffiliation* [Faculty] read
where the case of the attribute value in a given entry matches the ACL
as shown, and the eduPersonAffiliation attribute is
