hello all i want to know if is possible to have multiple suffix to same database
ex: suffix dc=exemple,dc=org suffix dc=msn,dc=com
any ideas
Buchan Milne writes:
On Monday 13 October 2008 17:37:14 Kermito le kermit wrote:
hello all i want to know if is possible to have multiple suffix to same database
ex: suffix dc=exemple,dc=org suffix dc=msn,dc=com
You can't (in modern versions of OpenLDAP).
He can try to compile with CPPFLAGS=-DBDB_MULTIPLE_SUFFIXES. I don't know if that code still works though.
Use multiple databases.
Yes, that's often the best way.
Still it is more cumbersome to maintain more databases. And there are some things that need a single database, like references between the two subtrees. (Aliases - which one should avoid anyway, possibly groups, I don't remember.)
----- "Hallvard B Furuseth" h.b.furuseth@usit.uio.no wrote:
Use multiple databases.
Yes, that's often the best way.
Still it is more cumbersome to maintain more databases. And there are some things that need a single database, like references between the two subtrees. (Aliases - which one should avoid anyway, possibly groups, I don't remember.)
I think time would better be spent in making useful things work across databases rather than revitalizing multiple suffixes in a single database. Another approach consists in making the database rooted at "", hiding "dc=org" and "dc=com" via 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 Fax: +39 0382 476497 Email: ando@sys-net.it -----------------------------------
Pierangelo Masarati wrote:
----- "Hallvard B Furuseth"h.b.furuseth@usit.uio.no wrote:
Use multiple databases.
Yes, that's often the best way.
Still it is more cumbersome to maintain more databases. And there are some things that need a single database, like references between the two subtrees. (Aliases - which one should avoid anyway, possibly groups, I don't remember.)
I think time would better be spent in making useful things work across databases rather than revitalizing multiple suffixes in a single database. Another approach consists in making the database rooted at "", hiding "dc=org" and "dc=com" via ACLs.
Agreed. Using suffix "" works already.
Pierangelo Masarati writes:
I think time would better be spent in making useful things work across databases rather than revitalizing multiple suffixes in a single database.
Shrug. I miss them sometimes - but not so much that I'm not volunteering do do the work. As far as I can tell the API always lacked proper support for them. Like a "suffix index" in the Operation structure which says which of the current database's suffixes caused dispatch to that backend/database.
Another approach consists in making the database rooted at "", hiding "dc=org" and "dc=com" via ACLs.
Unless you use the "referral" keyword.
Hallvard B Furuseth wrote:
Pierangelo Masarati writes:
I think time would better be spent in making useful things work across databases rather than revitalizing multiple suffixes in a single database.
Shrug. I miss them sometimes - but not so much that I'm not volunteering do do the work. As far as I can tell the API always lacked proper support for them. Like a "suffix index" in the Operation structure which says which of the current database's suffixes caused dispatch to that backend/database.
Agreed, the lack of this info from select_backend() was always a pain and too much effort to fix all the callers...
openldap-technical@openldap.org