Hello all,
Can we have users other than rootDN (specified in database config rootDN cn=config) to use the accessing database config?
Means can I configure an inetOrgPerson [stored in database bdb] to bind and use cn=config tree?
Now I am able to configure the rootDN as cn=config and search / modify the configuration entries
Please let me know how can I do this?
Thanks in advance,
Arunachalam.
**************************************************************************** **************************** This e-mail and attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient's) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!
Arunachalam Parthasarathy wrote:
Hello all,
Can we have users other than rootDN (specified in database config rootDN cn=config) to use the accessing database config?
Means can I configure an inetOrgPerson [stored in database bdb] to bind and use cn=config tree?
Now I am able to configure the rootDN as cn=config and search / modify the configuration entries
Please let me know how can I do this?
In OpenLDAP 2.3 you can set whatever identity as the rootdn of the config database, including the DN of an entry that is defined in another database. However, only the rootdn of the config database, whatever its identity is, can access the config database itself.
In OpnLDAP 2.4, the config database is accessible by regular users based on ACLs.
p.
Ing. Pierangelo Masarati OpenLDAP Core Team
SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it --------------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Email: pierangelo.masarati@sys-net.it ---------------------------------------
Arunachalam Parthasarathy writes:
Can we have users other than rootDN (specified in database config rootDN cn=config) to use the accessing database config?
Means can I configure an inetOrgPerson [stored in database bdb] to bind and use cn=config tree?
You can make rootdn the DN of that inetOrgPerson entry, instead of setting rootdn's password with rootpw.
openldap-software@openldap.org
-
Arunachalam Parthasarathy -
Hallvard B Furuseth -
Pierangelo Masarati