Re: -Y external and SUSE

Hi Stefan, can you please post the output from rpm -qf $(which ldapsearch) best regards Michael Am Mittwoch, dem 05.07.2023 um 20:37 +0200 schrieb Stefan Kania: > Hi to all, > > I just installed openSUSE 15.5 and the actual symas packages. After > installing OpenLDAP I could start slapd but

OpenLDAP 2.5 + GSSAPI + Kerberos

Total newbie here so please be gentle. I'm trying to set up a simple ldap server that uses SASL and Kerberos for authentication. I built OpenLDAP --with-cyrus-sasl and --enable-spasswd. I have the service principal and testsaslauthd works. I used slapadd to build the initial config (from

Re: -Y external and SUSE

Are you using the (suse) system ldapsearch, or ldapsearch that came with symas openldap? I have been bitten by that one. Try the other one, if you also have two. Op 05-07-2023 om 20:37 schreef Stefan Kania: Hi to all, I just installed openSUSE 15.5 and the actual symas packages. After

Re: -Y external and SUSE

Have you tried ldap.conf or ldaprc "URI" setting? On 6/07/2023 4:37 am, Stefan Kania wrote: Hi to all, I just installed openSUSE 15.5 and the actual symas packages. After installing OpenLDAP I could start slapd but "ldapsearch -Y external -H ldapi:///" is giving me a "can't connect to

-Y external and SUSE

Hi to all, I just installed openSUSE 15.5 and the actual symas packages. After installing OpenLDAP I could start slapd but "ldapsearch -Y external -H ldapi:///" is giving me a "can't connect to ldapserver" I found out that the ldap-socket on SUSE is (the same a on Debian systems) in

Re: mdb_env_close, mdb_dbi_close, mdb_dbi_open

I'll rephrase. For mdb_env_close: "Only a single thread may call this function". Is the meaning same as "For each environment, this function can be called at most once (from any thread)."? For mdb_dbi_close: "This call is not mutex protected. Handles should only be closed by a single thread".

Re: trying to understand SID portion in contextCSN

--On Wednesday, July 5, 2023 11:17 AM +0200 cYuSeDfZfb cYuSeDfZfb wrote: serverID 222 ldaps://ldapm01.company.com serverID 221 ldaps://ldapm02.company.com serverID 212 ldaps://ldapm03.company.com serverID 211 ldaps://ldapm04.company.com And when I (quick and dirty) check contextCSN using

trying to understand SID portion in contextCSN

Hi! Trying to better understand the contextCSN attribute. ContextCSN is formatted like: TIMESTAMP#COUNT#SID#MOD My question is on the SID part: ServerID. I have the following serverID configuration in our 4-server Multi-Master PoC setup: serverID 222 ldaps://ldapm01.company.com serverID 221