The problem with the various tutorials out on the net is that they are often incomplete, outdated, or sometimes just wrong.
Unfortunately, I too have found the official documentation a bit heavy on syntax description and a bit light on examples and how-tos.
So, I'd recommend double checking everything with the official docs if you choose to use external resources.
hint, "die.net" man pages show up first in google results. I am not sure they are out of date but I just go to the source. The openldap man pages are available here:
http://www.openldap.org/software/man.cgi
Tim Dunphy mailto:bluethundr@gmail.com February 19, 2014 at 5:03 PM Hey Dan,
Those docs you pointed me to worked beautifully! And thanks for the examples from your own config. I've used those too. Worked great! Thanks again.
Although I do also apprecaite the advice to read the official docs. Good advice, however the ones that I've been pointed to worked well for me. I'll read the official docs for a fuller understanding tho.
Tim
-- GPG me!!
gpg --keyserver pool.sks-keyservers.net http://pool.sks-keyservers.net --recv-keys F186197B
Dan Pritts mailto:danno@umich.edu February 19, 2014 at 2:08 PM I have simply
TLSCACertificateFile /etc/pki/tls/certs/ca-bundle.crt TLSCertificateFile /etc/pki/tls/certs/ldap.icpsr.umich.edu.crt TLSCertificateKeyFile /etc/pki/tls/private/ldap.icpsr.umich.edu.key
in my slapd.conf. CACertificateFile is almost certainly not required for a server cert.
Maybe you are running into an oddity of the cn=config? Have you tried just opening up the permissions to make sure the files are world readable? no selinux involved?
Folks on the list will probably yell at you to use the current version rather than the centos packages.
If you look through the archives for the last few weeks, you will find a pointer to a site that has rpm builds of current openldap.
