Our company was recently broken apart and certain segments were sold. Now I have to go through pull out all the parts that aren't staying with my particular organization (happens to be the one where the LDAP DB stays).
The problem is that my base dn, is based on the old company that is going away.
Is there a way I can make a new base dn, and then on the designated day, just switch to the new base?
In my ldap.conf it seems like I can only specify 1 base.
--Bryan
If I remember right, subtree rename are only supported with hdb. So if you're using hdb, you can probably configure stuff in such a way as to just do a MODRDN. If you're not using hdb, this is the perfect excuse for a downtime window to switch?
On Thu, 30 Nov 2006, Bryan Irvine wrote:
Our company was recently broken apart and certain segments were sold. Now I have to go through pull out all the parts that aren't staying with my particular organization (happens to be the one where the LDAP DB stays).
The problem is that my base dn, is based on the old company that is going away.
Is there a way I can make a new base dn, and then on the designated day, just switch to the new base?
In my ldap.conf it seems like I can only specify 1 base.
--Bryan
"Bryan Irvine" sparctacus@gmail.com writes:
Our company was recently broken apart and certain segments were sold. Now I have to go through pull out all the parts that aren't staying with my particular organization (happens to be the one where the LDAP DB stays).
The problem is that my base dn, is based on the old company that is going away.
Is there a way I can make a new base dn, and then on the designated day, just switch to the new base?
In my ldap.conf it seems like I can only specify 1 base.
there are a few options. 1. slapcat(8) a database dump to an ldif file, do a sed on this file to get rid of not required entries, slapdadd(8) this ldif file to a different database, you may have multiple backend and database definitions in slapd.conf 2. define a ldap database in slapd.conf and use this as proxy to your real database, you may define a rwm-suffixmassage statement in slapd.conf, to rewrite you suffix 3. create a new slapd.conf and a new database, run a second instance of slapd(8) listening on a different port and point your clients to this port.
-Dieter
openldap-software@openldap.org
-
Aaron Richton -
Bryan Irvine -
Dieter Kluenter