Version: 2.1 (using KDE 3.5.4, Kubuntu Package 4:3.5.4-0ubuntu2~dapper1 ) Compiler: Target: x86_64-linux-gnu OS: Linux (x86_64) release 2.6.15-26-amd64-k8 Neither Konqueror not Kuser can, connect in SSL mode though jxplorer (java app to manage ladap base) can ; I collect "certificate error" though certificates as pointed by file "slapd.conf" work for jxplorer. Do we have to indicate certificates as pointed by slapd to be usable for KDE apps and if yes how ? Regards
On the client side, you need to specify the certificates in /etc/openldap/ldap.conf or .ldaprc. A quick and dirty solution is to specify "TLS_REQCERT allow" in that file. In slapd.conf you specify certificates for the LDAP server running on the machine.
György for KAddressBook only the quick and dirty solution works fine for either TLS or SSL without SASL option ; if I comment out "TLS_REQCERT allow" in the ".ldaprc" file I collect the error message "error in certificates" ; so what is wrong with thoses certificates as built according to a toto and that work with other Java client apps ;any KDE app to generate certificates in location indicated in "/etc/ldap/sldap.conf" (with Ubuntu no /etc/openldap) ; now maybe you meant to also copy certificates lines in "/etc/ldap/ldap.conf" ? Regards.
Yes, maybe the right location is /etc/ldap/ldap.conf. The slapd.conf file is _always_ for the server! Or you can try alternative config file, there's pretty much possible locations and env variables, see man ldap.conf.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!