Learn more about these different git repos.
Other Git URLs
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
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.
On graceful shutdown remove the files that match a pattern.
milestone: NEEDS_TRIAGE => SSSD 1.2 owner: somebody => sgallagh
Bugizilla bug ... https://bugzilla.redhat.com/show_bug.cgi?id=584017
tests: 0 => 1
Fields changed
status: new => assigned
Fixed by a243a9f and 4f5664a
fixedin: => 1.2.0 resolution: => fixed status: assigned => closed
rhbz: => 0
Metadata Update from @rcritten: - Issue assigned to sgallagh - Issue set to the milestone: SSSD 1.2.0
SSSD is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in SSSD's github repository.
This issue has been cloned to Github and is available here: - https://github.com/SSSD/sssd/issues/1494
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.