Syncrepl Problems for Attribute-Value Pair host=*

Hello, I'm having a little syncrepl problem here. OL version is 2.3.13 + bdb 4.2.52 with 4 patches + OL transactions patch (is it still need?). We have a master server filled with mostly POSIX account and group data. I was experimenting to set up a slave slapd on a UNIX client which should

LDAP to RADIUS authentication bridge

On Sun, Dec 18, 2005 at 09:38:48PM +0100, Pierangelo Masarati wrote: I've written a FAQ entry from this: http://www.openldap.org/faq/data/cache/1299.html I wrote a backend for performing authentication against a RADIUS server. Using the sample config you gave me, I direct authentication to

Re: LDAP to RADIUS authentication bridge

On Mon, Dec 19, 2005 at 05:32:39PM +0100, Pierangelo Masarati wrote: The link seems to contain a SHA1 key; am I missing anything? Yes, sorry, that's fixed now, and the right SHA1 signature is SHA1 (ldap2radius-0.1.tgz) = ea27fe6d40c6c24b8799088bce35a6b4126dc89c If you think your code may be

Re: BerkeleyDB42.patch

I see that the file BerkeleyDB42.patch in the build directory was removed several weeks ago. I was wondering. If I already have BDB 4.2.52 compiled with that patch, is there a problem installing openldap 2.3.13 and using set_flags DB_LOG_AUTOREMOVE? Or should I recompile BDB w/out that

syncrepl configuration questions

Just a question on syncrepl directives. If using refreshAndPersist, is it true that you don't need to define sizelimit and timelimit inside the synrepl section of slapd.conf? Also, if you do define those, what is the proper syntax for unlimited? I recently turned up openldap-2.3.13 and when

Re: BerkeleyDB42.patch

--On Monday, December 19, 2005 6:05 PM +0100 Pierangelo Masarati [EMAIL PROTECTED] wrote: I see that the file BerkeleyDB42.patch in the build directory was removed several weeks ago. I was wondering. If I already have BDB 4.2.52 compiled with that patch, is there a problem installing

Re: syncrepl configuration questions

--On Monday, December 19, 2005 12:52 PM -0500 Dusty Doris [EMAIL PROTECTED] wrote: Just a question on syncrepl directives. If using refreshAndPersist, is it true that you don't need to define sizelimit and timelimit inside the synrepl section of slapd.conf? I never have. The defaults

Re: forcing password hash

At 11:57 AM 12/19/2005, Jim Boden wrote: Is there a way to force openldap to hash the userPassword entry if the client does not? As distributed, no. slapd(8) preserves the value of userPassword precisely as presented. But if the client does not use exop, is there anything we can do to

problem building comp_match module

Hallo everybody, I am trying to build comp_match module in openldap 2.3.13. Probably I am doing something wrong. First, I've done configure make depend make make install Second, I went into contrib/slapd-modules/comp_match and as it has been written in README modified path to snacc

Re: forcing password hash

Jim Boden wrote: That is exactly what I need. Thank you Howard! Can anyone tell me where are the pwd histories stored? I was working with another client that spoke exop and found that I could get pwd expiry to work, but not the quality settings or the history. They're stored in the user

Openldap 2.3.11 cannot autorecover from abnormal shutdown.

If the slapd was killed by SIGKILL(9), bdb database will be autorecovered at startup, I can read recovery message from 'slapd -d 5' But in some abnormal cases, such as power failure. slapd cannot autorecover at startup. It report: .. slapd startup: initiated. backend_startup_one: starting