--On Thursday, September 01, 2005 11:52 AM +0530 Rohit Kumar (rokumar)
[EMAIL PROTECTED] wrote:
Hi,
I am having problems with slapadd process.
I am using the following command line after shutting down the slapd
process:
/opt/openldap/sbin/slapadd -c -f
run slapd in debug mode (slapd -d x), where x = level. View man
slapd.conf for debug option levels.
chap.
On 8/31/05, Jesus Bernardo Ruiz Flores [EMAIL PROTECTED] wrote:
Is there a way to view the request dn that cyrus-sasl send to ldap, i
have to test my sasl-regexp, but in the ldap debug
Buchan Milne wrote:
DB settings from slapd.conf:
backend bdb
checkpoint 512 30
cachesize = 2000
idlcachesize = 6000
I hope the two equal signs above have been added by you writing the
email, cause they're not legal in slapd.conf and slapd
On 9/1/05, Luca Scamoni [EMAIL PROTECTED] wrote:
Buchan Milne wrote:
DB settings from slapd.conf:
backend bdb
checkpoint 512 30
cachesize = 2000
idlcachesize = 6000
I hope the two equal signs above have been added by you writing the
Hello everyone,
In the access controls, you can specify all attributes allowed in an
objectclass by using the @ notation. Is there a way to do something
like @inetOrgPerson, -cn so indicate all the attributes allowed in
inetOrgPerson but not the cn attribute? (this is obviously just an
example)
On Thu, 2005-09-01 at 10:12 +0200, Diego de Felice wrote:
1) After a failover to the secondary master, what should we do with the
primary? What if the primary comes back online? The simplest solution is
provided by that article pointed out by Gary: prevent the failed node to
re-acquire the
Hello everyone,
In the access controls, you can specify all attributes allowed in an
objectclass by using the @ notation. Is there a way to do something
like @inetOrgPerson, -cn so indicate all the attributes allowed in
inetOrgPerson but not the cn attribute? (this is obviously just an
That seems to work. Except since I was doing a none for the
individual attribute, it only works when I specify it first as such:
access to attrs=cn
by dn.exact=cn=someone none
access to [EMAIL PROTECTED]
by dn.exact=cn=someone read
On Thu, 2005-09-01 at 18:09 +0200, Pierangelo
To reset a user's LDAP account that has been locked
due maxFailure bind failures, my client program
performs the following steps:
On the user entry that is locked:
set userPassword = to a new password value
set pwdReset = TRUE
delete pwdLockedTime operational attribute
Testing w/ version
Samuel Tran wrote:
Hi All,
I would like to make my OpenLDAP setup more fault-tolerant by introducing
a second master server.
There are a couple of high-avalaibility solutions, Heartbeat + DRDB being
one of them.
If any of you have already implemented such a solution with your OpenLDAP
setup,
In revision 1.58 I updated the operational attribute schema to match
draft 9 of the password policy specification; it makes a number of
attributes non-user-modifiable, including pwdAccountLockedTime. We may
have to back out a couple more of these changes if there is no internal
mechanism to
Perry Nguyen wrote:
Ando,
Being able to customize the timeout is handy and all, but my main
interest is in why JNDI behaves strangely with back-meta and
back-ldap, slapd keeps returning no results whenever the query comes
from a Java JNDI client. My primary interest with this (problem) is
12 matches
Mail list logo
