Red Hat Bugzilla – Bug 581569
Authconfig should use certmonger to track LDAP certificates
Last modified: 2011-06-02 14:47:59 EDT
Description of problem:
When setting up LDAP for authentication (as opposed to simply for identities), it is mandatory for the communication to be protected by either SSL or TLS. This means that a trusted CA certificate must be available. In the majority of deployments, the LDAP server will not have a certificate signed by any of the trusted authorities installed by default on the system.
This is why the "Download CA certificate" button exists. However, there remains a problem in that the downloaded certificate will eventually expire. This will cause authentications against LDAP to suddenly fail, with a cryptic connection error in the logs.
With certmonger, it's possible to track the CA certificate, which will report to the syslog when the certificate is approaching expiration, and when it actually has expired. This should make life much easier when debugging connection failures.
Version-Release number of selected component (if applicable):
Certmonger has a command-line interface as well as a D-BUS system bus interface for requesting that it track certificates.
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '13'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 13's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 13 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here: