Unconfiguring sssd leaves KDC locator file

[sssd-bot]

Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/452

• Created at 2010-04-16 00:07:06 by rcritten
• Closed as Fixed
• Assigned to sgallagh

---

I'm having problems with kerberos on a system that had sssd configured then unconfigured.

I installed and configured sssd via the ipa-client-install script. It invokes authconfig to do the install:

/usr/sbin/authconfig --enablesssd --enablesssdauth --update

I unconfigure with:

/usr/sbin/authconfig --disableldap --disablekrb5 --disablesssd --disablesssdauth --update

It left the file /var/lib/sss/pubconf/kdcinfo-REALM

This is overriding my krb5.conf settings, pointing the client to the wrong KDC making kerberos not work.

Removing this file makes kerberos work as expected.

sssd-1.0.5-1.fc12.x86_64

Comments

---

Comment from sbose at 2010-04-16 11:28:39

One solution might be that the locator plugin should only run if a special environment variable is set. The sssd components can set the variable by themselves and pam_sss can set it for sessions which where authenticated by sssd. If users not handled by sssd, e.g. root, want to let the locator plugin resolve the KDC they have to set this variable manually.

---

Comment from dpal at 2010-04-20 15:20:04

On graceful shutdown remove the files that match a pattern.

milestone: NEEDS_TRIAGE => SSSD 1.2
owner: somebody => sgallagh

---

Comment from jgalipea at 2010-04-20 16:25:21

Bugizilla bug ... https://bugzilla.redhat.com/show_bug.cgi?id=584017

tests: 0 => 1

---

Comment from sgallagh at 2010-05-04 23:07:41

Fields changed

status: new => assigned

---

Comment from sgallagh at 2010-05-10 14:59:38

Fixed by a243a9f and 4f5664a

fixedin: => 1.2.0
resolution: => fixed
status: assigned => closed

---

Comment from dpal at 2012-01-19 02:45:32

Fields changed

rhbz: => 0

---

Comment from rcritten at 2017-02-24 14:56:05

Metadata Update from @rcritten:

• Issue assigned to sgallagh
• Issue set to the milestone: SSSD 1.2.0