Groups | Search | Server Info | Login | Register


Groups > comp.protocols.kerberos > #5371

Restoring DB to alternate LDAP suffix

From Jake Scott <jake@poptart.org>
Newsgroups comp.protocols.kerberos
Subject Restoring DB to alternate LDAP suffix
Date 2025-01-29 12:00 -0500
Organization TNet Consulting
Message-ID <mailman.142.1738177827.2322.kerberos@mit.edu> (permalink)
References <CAExmWcgam_XtE+32_weR_hrO1ZDb-irNpWCaP0QxA3_c9zfcyw@mail.gmail.com>

Show all headers | View raw


Hi there..

We are currently migrating data from an LDAP backend (MIT v1.18) to a new
suffix. We've dumped the data using kdb5_util and are attempting to restore
it using a new configuration with the updated suffix.

During the restore process, it appears that the principals are being added
back using their original DNs instead of under the new suffix. Is this
expected behavior? We were surprised to find the principal DNs included in
the dump file.

Any insight or advice would be much appreciated!


Thanks..

Jake

Back to comp.protocols.kerberos | Previous | Next | Find similar


Thread

Restoring DB to alternate LDAP suffix Jake Scott <jake@poptart.org> - 2025-01-29 12:00 -0500

csiph-web