#2313 consider going offline on KRB5KRB_ERR_GENERIC error instead of System Error
Closed: Fixed None Opened 9 years ago by jhrozek.

In some rare cases (one was dirsrv segfaulting in an IPA setup) krb5_child gets back KRB5KRB_ERR_GENERIC which propagates into System Error, so the user can't log in.

We should consider going offline instead, so that user can log in with his cached credentials and maybe use another alive replica for the next request.

Fields changed

owner: somebody => preichl

Fields changed

patch: 0 => 1

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.12 beta

Fields changed

resolution: => fixed
status: new => closed

Fields changed

rhbz: => 0

Metadata Update from @jhrozek:
- Issue assigned to preichl
- Issue set to the milestone: SSSD 1.12 beta

6 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/3355

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.