This is starting to make more sense. I found the OpenLDAP v2.6 repos that are provided by Symas at repo.symas.com, and I was able to install it for Ubuntu 20.04.
Unfortunately, it now appears that I can't use "slapcat". I just installed `ldap-utils` again from the base Ubuntu repositories (I couldn't find ldap-utils in the Symas repos), so I can now run "ldapsearch" again, but am currently troubleshooting with some search results that may or may not just be my fault and inexperience using this software. I'll keep digging. But to confirm, is it OK to use the Ubuntu "ldap-utils" package along side the Symas-provided ldap server packages? Sent with ProtonMail Secure Email. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Tuesday, January 4th, 2022 at 6:43 AM, David White <[email protected]> wrote: > Thank you, Quanah. > > Is the recommendation to go with v2.5 or 2.6 because of limited features in > v2.4 for what I'm trying to do? My concern is that we have several OpenLDAP > servers, and we need to maintain the servers going forward. Obviously we can > recompile, but that just adds complexity to our company's infrastructure that > is already handled by a distributed team, and if at all possible, we'd prefer > to use distro-provided packages. > > That said, if there's a good reason that v2.4 won't be as easy to configure > to do what I need it to do, then I think I can sell my boss on the idea. We > just need to have a good patching plan in place going forward for these > systems. > > I did realize that back-ldap is required. I made a silly mistake, and was > trying to load a completely different module in slapd.conf (question and my > own answer at > https://serverfault.com/questions/1088505/openldap-push-replication-via-proxy-guide-to-setup-syncrepl/1088577#1088577 > on the topic). > > However, as I mentioned before, I'd really like to figure out how to build > this system using ldif instead of the old .conf format. All of the guides > I've been able to find thus far seem to reference the old .conf format, and > only refer to basic proxy setups -- I still haven't been able to find any > clear instructions on how to setup an overlay on the same system, with a > push-based configurations. > > Sent with ProtonMail Secure Email. > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ > > On Monday, January 3rd, 2022 at 11:46 AM, Quanah Gibson-Mount > [email protected] wrote: > > > --On Thursday, December 23, 2021 3:32 PM +0000 David White > > > > [email protected] wrote: > > > > > Thank you for your response and for nudging me towards the test scripts. > > > > > > Shortly after your email, I had to deal with an emergency, so am only now > > > > > > circling back around to this. > > > > > > I currently have the "ldap-utils" package installed from the base Ubuntu > > > > > > repositories on Ubuntu 20.04. This is version 2.4.49 of openldap. > > > > > > I then downloaded the source code for openldap-2.5.9, and have figured > > > > > > out how to run "make test" to run all of the test scripts. > > > > > > Unfortunately, the test045 script keeps failing because it says that the > > > > > > necessary backend isn't even available, which is really confusing to me, > > > > > > because I've ensured that back-mdb is enabled. > > > > > > See below for output of `slapcat` as well as the modules enabled. Why is > > > > > > the test045 script telling me that the "LDAP backend not available, test > > > > > > skipped" when back-mdb and syncprov are both clearly available? Am I > > > > > > missing something else? > > > > The "ldap backend" is back-ldap. back-ldap is required to do proxied > > > > syncreplication. > > > > I'd suggest ignoring the Ubuntu packages entirely and using the free 2.5 or > > > > 2.6 packages provided by Symas for Ubuntu. > > > > Regards, > > > > Quanah > > > > Quanah Gibson-Mount > > > > Product Architect > > > > Symas Corporation > > > > Packaged, certified, and supported LDAP solutions powered by OpenLDAP: > > > > http://www.symas.com
publickey - [email protected] - 0x320CD582.asc
Description: application/pgp-keys
signature.asc
Description: OpenPGP digital signature
