Learn more about these different git repos.
Other Git URLs
Patch 5e88215 the useful functionality that kpasswdinfo file is always created, not only during change password operations. But if the kpasswd server cannot be resolved the authentication fails as well, although the kpasswd server is not needed for authentication.
If the kpasswd server cannot be resolved during an authentication request the error should just be ignored and authentication should continue.
Reproducer: Set krb5_kpasswd to a non existing name.
owner: somebody => jhrozek
status: new => assigned
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=847039
rhbz: => [https://bugzilla.redhat.com/show_bug.cgi?id=847039 847039]
milestone: NEEDS_TRIAGE => SSSD 1.9.0 RC2
I know this bug was planned to be fixed in RC2 but I suspect that it might be the root cause of a problem we've been seeing in production, so I fixed it sooner.
patch: 0 => 1
proposed_priority: => Blocker
resolution: => fixed
status: assigned => closed
Metadata Update from @sbose:
- Issue assigned to jhrozek
- Issue set to the milestone: SSSD 1.9.0 RC1
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:
If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.
Thank you for understanding. We apologize for all inconvenience.
to comment on this ticket.