Hi,
Ok
my rule is
access to
dn.regex=^mail=([^,]+),ou=([^,]+),jvd=([^,]+),o=hosting,dc=myhosting,dc=example$
attrs=userPassword
by
dn.exact=mail=$1,ou=$2,jvd=$3,o=hosting,dc=myhosting,dc=example write
by
Hello,
Based on this article:
http://www.rexconsulting.net/ldap-protocol-uidNumber.html.
I am trying to increment 'uidNumber'. For doing that, I am using this
LDIF file:
--- autoinc.ldif ---
dn: cn=uidNext,dc=example,dc=com
changetype: modify
Thank you very much. It works well now!
Pablo.
On 12/21/2011 10:04 AM, Dieter Klünter wrote:
Am Wed, 21 Dec 2011 09:37:10 -0300
schrieb Pablopaa.lis...@gmail.com:
Hello,
Based on this article:
http://www.rexconsulting.net/ldap-protocol-uidNumber.html.
I am trying to increment
Thank you! This also works (with a minor change):
This is the LDIF that I use:
--- increment.ldif ---
dn: cn=uidNext,dc=example,dc=com
changetype: modify
increment:uidNumber
uidNumber: 1
-
EOF --
Pablo.
On 12/21/2011
Torsten Schlabach (Tascel eG) wrote:
Hi Quanah!
First of all: Thanks for answering the original question. I was wondering
first why changes to the database content as such have been persisted and
the new contextCSN hasn't until I found that this syncprov-checkpoint thing
actually belongs to the
--On Wednesday, December 21, 2011 4:36 PM + Torsten Schlabach (Tascel
eG) tschlab...@tascel.net wrote:
We're using OpenLDAP 2.4.23 on Debian Linux. The backend is a
back-hdb.
Upgrade.
Actually, yes, newer is better most of the time in OSS land, but still, in
a production system IMO
Dear Ralf,
Hi, I hope you are still here before the holidays, I would appreciate your
advice and counsel.
I have Suse 12.1 up, mile stone 5. It works well.
I have installed and used ldap 2.4.26.
It is also working with nss_ldap code.
I am having some trouble on 2 counts.
First I tried to get
I'm using TLS but would like to force clients to connect using TLS sans the
loopback device or LDAP server itself.
I found this post from 2006 which suggests the following.
It doesn't work for me:
# first, make sure TLS or localhost
access to *
by tls_ssf=1 none break
--On Wednesday, December 21, 2011 4:11 PM -0500 Michael Starling
mlstarlin...@hotmail.com wrote:
My current real ACLS'
10.3.5.205 is the IP address of the system on the loopback interface.
These settings still allow any system to connect without using TLS.
If I change the line in the last
