Learn more about these different git repos.
Other Git URLs
We could write a unit test that would create a keytab with different principals using ktutil, and then attempt to select the correct principal using the selection algorithm in sss_krb5.c
The principal selection would be wrapped in a simple CLI program that would be executed from the unit test script which might be written in Python to ease interaction with ktutil.
Fields changed
keywords: => easyfix milestone: NEEDS_TRIAGE => SSSD 1.10 beta priority: major => minor rhbz: => 0 type: defect => task
selected: => Not need
Moving tickets that are not a priority for SSSD 1.10 into the next release.
milestone: SSSD 1.10 beta => SSSD 1.11 beta
changelog: => design: => design_review: => 0 fedora_test_page: => milestone: SSSD 1.13 beta => Interim Bucket review: => 0
priority: minor => major
milestone: Interim Bucket => SSSD 1.12 beta
blocking: => #1923
milestone: SSSD 1.12 beta => SSSD 1.12.1
Mass-moving all tickets that didn't make 1.12.1 into 1.12.2
milestone: SSSD 1.12.1 => SSSD 1.12.2
We need to do a release as requested by downstream. Moving tickets that are not fixed already or very close to acking to 1.12.3
milestone: SSSD 1.12.2 => SSSD 1.12.3
It makes sense to write the unit tests now instead of moving them to a later release again, but the tickets in 1.12.3 should be more focused at this point. Moving to 1.12.4
mark: => 0 milestone: SSSD 1.12.3 => SSSD 1.12.4
owner: somebody => preichl
milestone: SSSD 1.12.4 => SSSD Deferred
Metadata Update from @jhrozek: - Issue assigned to preichl - Issue marked as blocked by: #1923 - Issue set to the milestone: SSSD Patches welcome
Metadata Update from @jhrozek: - Assignee reset - Custom field blocking reset (from #1923) - 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 testsupdated reset (from 0) - Issue close_status updated to: None - Issue tagged with: easyfix
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)
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/2580
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.