[Date Prev][Date Next]
Re: Adding OU with PSQL backend
Marcel Berteler wrote:
For a project that requires a large user authentication database, we are
currently using OpenLDAP with a BDB backend. We have about 150K users in
the tree and all works well. Authentication and new user creation is
fast and we are happy.
But, when we try and get statistical data from the tree, we run into the
limitations of LDAP: trying to find all user that have registered last
month, using a filter with 2 dates, is just too slow. It takes minutes
to come back with a result.
To get around this limitation, we want to experiment with a PSQL backend
so we can do some comparative testing.
(If any of you have a way of allowing us to interrogate our BDB backend
with SQL like queries that are relatively fast, than please let me know.)
Our test environment:
openldap 2.4.16 with Postgres backend
I have loaded CORE in slapd.conf as well as our custom schema for our users
The only ACL in the conf is ACCESS TO * BY * WRITE
Our tree looks like this and I have loaded the data tables and meta-data
The setup is working about 60%.
with openLdapAdmin, I can see the tree and I can add users.
What I can not do, is add an OU. It gives me:
LDAP said: Server is unwilling to perform
Error number: 0x35 (LDAP_UNWILLING_TO_PERFORM)
Description: The LDAP server refused to perform the operation.
If I get this on our custom schema, I can explain this by not having the
right meta-data and procedures loaded. But as this is part of the CORE
schema, am I right in only adding the meta-data for OU in
ldap_attr_mappings without add or delete procedures?
No you're not. There is no core schema mapping in back-sql, everything
needs to be mapped by you, including core schema items. In fact,
back-sql's logic has no notion of attributes per se, but only of
attributes in some relationship with (structural) objectClasses
according to the mappings you define.
If you mapped, say, "cn" for "person", don't expect to be able to use
"cn" in, say, "inetOrgPerson" or "device". You need a separate "cn"
mapping for each objectClass that needs to use it.
I have looked at the log files and outputs but I can not figure out what
is going wrong and why it is not accepting any new OU
Maybe if you let others look at your logs, others can figure it out for you.
Let me anticipate that since you're using OpenLDAP 2.2.6, there is no
chance any issue can get fixed.
Ing. Pierangelo Masarati
OpenLDAP Core Team
via Dossi, 8 - 27100 Pavia - ITALIA
Office: +39 02 23998309
Mobile: +39 333 4963172
Fax: +39 0382 476497