Bug 549804 - system-config-authentication - enabling sssd - should populate configuration options with existing configuration
system-config-authentication - enabling sssd - should populate configuration ...
Product: Fedora
Classification: Fedora
Component: authconfig (Show other bugs)
All Linux
high Severity medium
: ---
: ---
Assigned To: Tomas Mraz
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2009-12-22 13:03 EST by Jenny Galipeau
Modified: 2010-10-05 10:27 EDT (History)
5 users (show)

See Also:
Fixed In Version: authconfig-6.1.2-1.fc13
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-10-05 10:27:40 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jenny Galipeau 2009-12-22 13:03:53 EST
Description of problem:
If a machine is already configured for authentication and identities, (i.e. ldap identities and kerberos authentication) - enabling SSSD should be as simple as enabling the check box.  All required existing configuration is known and should be automatically shown in the GUI. 

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

How reproducible:

Steps to Reproduce:
1. Configure machine for kerberos authentication and ldap identities. 
2. Install sssd
   yum install sssd sssd-client
2. As root launch, system-config-authentication
3. Select the SSSD settings tab
4. Enable the check box for "Enable SSSD support"
Actual results:
No default domain is configured with the existing configuration

Expected results:
Default domain to be add with the correct kerberos authentication provider and ldap identity provider already shown and properly configuraed.

Additional info:
Comment 1 Daniel Walsh 2009-12-22 14:43:55 EST
This gui should be greatly simplified.  Everything should be defaulted and there should be very few options.  If I want advanced settings, I need to go in and edit the config file.  

I used the machine on a machine that had ldap and kerberos already configured, within the tool.  All I should have had to do was click on use sssd.

sssd should be all about simplifying stuff, this is far too complicated.

You need to work with Maureen Duffy on the GUI.
Comment 2 Tomas Mraz 2009-12-22 15:45:33 EST
I've said that on the telecon where we discussed the authconfig sssd support first. I proposed there much simpler UI with just a few use-cases supported but there was objection that complete configuration with multiple domains and freely selectable providers for the domains should be supported from start.

To be able to implement this I need the typical use cases which should be supported.
Comment 3 Daniel Walsh 2009-12-22 15:53:30 EST
I was not on the call.  :^(

I think we have time to work with Maureen and get a solution that 90% of users would do.  Leave the complicated stuff to graphical vim editing of /etc/sssd/sssd.conf to the experts.

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