#1316 kpasswd server status set to working when Kerberos auth succeeds
Closed: Fixed None Opened 10 years ago by jhrozek.

https://bugzilla.redhat.com/show_bug.cgi?id=817941 (Red Hat Enterprise Linux 6)

Description of problem:
There is a logic bug in the Kerberos provider that, if a dedicated kpasswd
server is used, causes the kpasswd server status to be reset to working
whenever Kerberos auth succeeds.

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

How reproducible:

Steps to Reproduce:
1. set dedicated krb5_server and kpasswd server lists:
krb5_server = foo.example.com, bar.example.com
krb5_kpasswd = foo.example.com, bar.example.com
2. shut down the KDC and kpasswd servers on foo.example.com
3. authenticate

Actual results:
the fail over authenticates against bar.example.com, but the status of the
kpasswd server foo.example.com will be set to working.

Expected results:
the kpasswd server status should not be changed during authentication.

Fields changed

blockedby: =>
blocking: =>
coverity: =>
feature_milestone: =>
owner: somebody => jhrozek
patch: 0 => 1
status: new => assigned
tests: => 0
testsupdated: => 0
upgrade: => 0

Fixed in 4e3b55b

milestone: NEEDS_TRIAGE => SSSD 1.9.0
resolution: => fixed
status: assigned => closed

Fields changed

milestone: SSSD 1.9.0 => SSSD 1.9.0 beta 1

Metadata Update from @jhrozek:
- Issue assigned to jhrozek
- Issue set to the milestone: SSSD 1.9.0 beta 1

5 years ago

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/2358

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.

Login to comment on this ticket.