Red Hat Bugzilla – Bug 578311
authconfig doesn't remember "[X] Use TLS to encrypt connection" setting
Last modified: 2013-09-02 02:47:04 EDT
Created attachment 403599 [details]
Description of problem:
Start authconfig-gtk and setup LDAP+TLS identity and authentication as detailed in https://fedoraproject.org/wiki/QA:Testcase_SSSD_LDAP_Identity_and_LDAP_Authentication_with_TLS. When done, apply changes. Restart authconfig-gtk, and see that "[ ] Use TLS to encrypt connection" is not enabled.
Version-Release number of selected component (if applicable):
* 3 of 3 attempts
Steps to Reproduce:
1. Configure LDAP+TLS identity and LDAP auth as detailed in https://fedoraproject.org/wiki/QA:Testcase_SSSD_LDAP_Identity_and_LDAP_Authentication_with_TLS
2. Apply changes and close s-c-authentication
3. Start s-c-authentication
See screenshot. The TLS is not enabled, despite being enabled and applied at during the previous attempt.
All previous settings should be reflected in the gui when restarting s-c-authentication
The TLS setting gets lost every time that the authentication provider is switched.
It seems that although the sssd.conf file contains ldap_id_use_start_tls = True the SSSDConfig API call returns False.
Ticket opened upstream: https://fedorahosted.org/sssd/ticket/441
sssd-1.1.1-1.fc13 has been submitted as an update for Fedora 13.
sssd-1.1.1-1.fc12 has been submitted as an update for Fedora 12.
sssd-1.1.1-1.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update sssd'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/sssd-1.1.1-1.fc13
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
sssd-1.2.2-18.fc13 has been submitted as an update for Fedora 13.
sssd-1.2.2-19.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.