Bug 625439 - Authconfig --updateall doesn't update SSSD configuration
Summary: Authconfig --updateall doesn't update SSSD configuration
Alias: None
Product: Fedora
Classification: Fedora
Component: authconfig   
(Show other bugs)
Version: 13
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Tomas Mraz
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2010-08-19 12:58 UTC by Stephen Gallagher
Modified: 2011-06-28 14:24 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2011-06-28 14:24:19 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Stephen Gallagher 2010-08-19 12:58:14 UTC
Description of problem:
The following command does not set up SSSD configuration:
authconfig  --updateall \
--enableldap --ldapbasedn=dc=example,dc=com \
--ldapserver="ldap://ldap.example.com" \
--enablekrb5 \
--krb5kdc="kerberos.example.com" \
--krb5adminserver=kerberos.example.com \

On a clean system, this results in SSSD failing to start, as the config file hasn't been written.

authconfig  --kickstart \
--enableldap --ldapbasedn=dc=example,dc=com \
--ldapserver="ldap://ldap.example.com" \
--enablekrb5 \
--krb5kdc="kerberos.example.com" \
--krb5adminserver=kerberos.example.com \

does work as expected. The only difference between these commands is that the first uses --updateall and the second uses --kickstart.

Version-Release number of selected component (if applicable):

How reproducible:
Every time

Steps to Reproduce:
1. Provision a clean system or delete /etc/sssd/sssd.conf
2. Run the above command
Actual results:
/etc/sssd/sssd.conf is not written, and SSSD fails to start.

Expected results:
/etc/sssd/sssd.conf should be written out with a valid [domain/default] section

Additional info:

Comment 3 Tomas Mraz 2010-08-19 13:14:50 UTC
This is fixed already in F14/Rawhide.

Comment 4 Stephen Gallagher 2010-08-19 13:27:56 UTC
Are there plans to backport the fix for Fedora 13?

Comment 5 Tomas Mraz 2010-08-19 13:38:08 UTC
No plans, but I can do that, I'll update authconfig with new upstream release, reverting stuff that is not F-13 compatible.

Comment 6 Bug Zapper 2011-06-01 11:08:21 UTC
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: 

Comment 7 Bug Zapper 2011-06-28 14:24:19 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.