#1518 [RFE] Better diagnose keytab mismatch
Closed: wontfix 4 years ago by pbrezina. Opened 11 years ago by dpal.

There have been different issues reported on the list in the past related to the hard to detect misconfigurations of kerberos. It would be nice to be able to automatically detect some of such issues and report them.
For example thread https://lists.fedorahosted.org/pipermail/sssd-users/2012-September/000168.html was talking about mismatch of the kerberos encryption types and encryption types available in the keytab.
If we can look at the keytab and validate that the principal is correct, that all required encryption types are present and so on and report all issues in advance we would save a lot of time for our community, customers and support.


Fields changed

type: defect => enhancement

Fields changed

summary: [RFE] Bette diagnose keytab mismatch => [RFE] Better diagnose keytab mismatch

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.11 beta
rhbz: => 0
type: enhancement => task

Fields changed

milestone: SSSD 1.11 beta => SSSD 1.12 beta

Fields changed

type: task => enhancement

This ticket makes sense, but the 1.14 milestone is already too big. I'm moving the ticket to 1.15 beta

changelog: =>
design: =>
design_review: => 0
fedora_test_page: =>
mark: => 0
milestone: SSSD 1.14 beta => SSSD 1.15 beta
review: => 0
selected: =>
sensitive: => 0

Metadata Update from @dpal:
- Issue set to the milestone: SSSD Future releases (no date set yet)

7 years ago

Metadata Update from @thalman:
- Custom field design_review reset (from 0)
- Custom field mark reset (from 0)
- Custom field patch reset (from 0)
- Custom field review reset (from 0)
- Custom field sensitive reset (from 0)
- Custom field testsupdated reset (from 0)
- Issue close_status updated to: None
- Issue tagged with: Canditate to close

4 years ago

Thank you for taking time to submit this request for SSSD. Unfortunately this issue was not given priority and the team lacks the capacity to work on it at this time.

Given that we are unable to fulfill this request I am closing the issue as wontfix.

If the issue still persist on recent SSSD you can request re-consideration of this decision by reopening this issue. Please provide additional technical details about its importance to you.

Thank you for understanding.

Metadata Update from @pbrezina:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

4 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/2560

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.

Metadata