Bug 598556 - authconfig should not touch any sssd domain that is not named "default"
authconfig should not touch any sssd domain that is not named "default"
Product: Fedora
Classification: Fedora
Component: authconfig (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Tomas Mraz
Fedora Extras Quality Assurance
Depends On:
Blocks: 598558
  Show dependency treegraph
Reported: 2010-06-01 11:43 EDT by Simo Sorce
Modified: 2010-06-10 11:51 EDT (History)
2 users (show)

See Also:
Fixed In Version: authconfig-6.1.6-1.fc14
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 598558 (view as bug list)
Last Closed: 2010-06-10 11:51:46 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 Simo Sorce 2010-06-01 11:43:29 EDT
Apparently the current behaviour of authconfig is to "take over" the first domain listed in sssd and reconfigure it.

Authconfig shouldn't do that as it will destroy potentially valuable configuration.

Authconfig should always only use "default" as domain name and add it to the list of currently active domains.

This avoid irreparably destroying a currently working configuration if authconfig is misused on a machine that already has working domains configured.

Note: authconfig may decide to rewrite the "domains" option in [sssd] instead of just appending. This will cause the deactivation of other configured domains, but at least it will not destroy their configuration and all a user needs to do is to change back the "domains" option to include the right domains.

Also note: a non working domain does not affect other domains. If a domain fails sssd will go on consulting all the others and will log the issue to the log files.

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