openldap-technical March 2020

openldap-technical@openldap.org

22 participants
27 discussions

Re: With MDB Openldap seems to be pretty slower in Windows
by Vijay Kumar 01 Mar '20

01 Mar '20

Thank Quanah, for the response. Can i request to let me know what is WSLv2 you meant for? -Vijay Kumar On Fri, Feb 28, 2020 at 10:52 PM Quanah Gibson-Mount <quanah(a)symas.com> wrote: > --On Friday, February 28, 2020 8:58 AM -0800 Quanah Gibson-Mount > <quanah(a)symas.com> wrote: > > >> We have a 110 users data by performance testing, where we observed > >> slowness for windows 10 OS. > > > > This is not a topic for -devel, please post to -technical instead. > > Ugh, even worse, you double posted. DO NOT DOUBLE POST. > > I would suggest testing WSLv2. ;) > > --Quanah > > > -- > > Quanah Gibson-Mount > Product Architect > Symas Corporation > Packaged, certified, and supported LDAP solutions powered by OpenLDAP: > <http://www.symas.com> > -- Thanks & Regards, Vijay Kumar *+91-94944 44009*

2 1

SASL domain no longer recognised
by Rick van Rein 01 Mar '20

01 Mar '20

Hello, I have a demo setup with slapd on Debian Stable, and a while back followed Debian's Switch to Buster, with slapd 2.4.47. Since about that time, slapd stopped recognising its SASL realm. This is in a dev/demo/test environment in Docker, so naming is a bit silly, but that always worked. Config and such are shown at https://github.com/arpa2/docker-demo/tree/master/demo-reservoir Using "ldapsearch -Y GSSAPI -H ldap://reservoir.arpa2:1388 -b ou=Reservoir,o=arpa2.net,ou=InternetWide" gives the message SASL/GSSAPI authentication started ldap_sasl_interactive_bind_s: Other (e.g., implementation specific) error (80) additional info: SASL(-1): generic failure: GSSAPI Error: Unspecified GSS failure. Minor code may provide more information (No key table entry found matching ldap/reservoir.arpa2@) **In this output, note the lacking realm after the @.** This appears to be a server-side issue, because the client had the realm in the klist output and that name is present in the keytab: 02/29/20 11:54:53 02/29/20 21:47:26 ldap/reservoir.arpa2(a)ARPA2.NET renew until 03/01/20 11:47:22 The configuration of the server in /etc/ldap/slapd.conf still says: sasl-host reservoir.arpa2 sasl-realm ARPA2.NET FWIW, slapd runs as /usr/sbin/slapd -d any -h "ldapi://%2ftmp%2fldap-socket ldap://:1388/" Have I missed changes to slapd? Are there log messages that I overlooked (or should selected for)? Thanks! -Rick

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

openldap-technical March 2020