Learn more about these different git repos.
Other Git URLs
MIT dev team is working on the new type of the credential cache to support the case when one user has multiple tickets for different Kerberos realms. This is a feature of Kerberos 1.10. We need to take advantage of this functionality as soon as it becomes available.
http://k5wiki.kerberos.org/wiki/Projects/Client_principal_selection
Fields changed
owner: somebody => jzeleny
milestone: NEEDS_TRIAGE => SSSD 1.9.0 summary: Implement new credential cache type in SSSD => Integrate with new MIT implementation of the credential cache
The client principal selection method works great in MIT Krb5 1.10 Any chance we can anticipate support in SSSD master so I can do long term testing ?
blockedby: => blocking: =>
Moving to NEEDS_TRIAGE for evaluation
milestone: SSSD 1.9.0 => NEEDS_TRIAGE
milestone: NEEDS_TRIAGE => SSSD 1.9.0
milestone: SSSD 1.9.0 => SSSD Kerberos improvements
priority: major => critical
rhbz: => 0
Pulling back out to NEEDS_TRIAGE. I think we need to have this earlier than 1.11, as it should really aim to land in Fedora 18.
component: SSSD => Kerberos Provider feature_milestone: => milestone: SSSD Kerberos Improvements Feature => NEEDS_TRIAGE summary: Integrate with new MIT implementation of the credential cache => Support DIR: credential caches for multiple TGT support type: defect => enhancement
summary: Support DIR: credential caches for multiple TGT support => [RFE] Support DIR: credential caches for multiple TGT support
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=805917
rhbz: 0 => [https://bugzilla.redhat.com/show_bug.cgi?id=805917 805917]
milestone: NEEDS_TRIAGE => SSSD 1.10 beta
milestone: SSSD 1.10 beta => SSSD 1.9.0 beta 2
owner: jzeleny => jhrozek status: new => assigned
patch: 0 => 1
Fixed by:
- 727937fb86cfb042063f02fa2a229d236d7f105f - 3ca7450bc821ac37851e92a256d0a2b89f4f2032 - 248a24eda712d738127897264290ad1b751faf12 - 7b14a9e64fd248103149eb1cb422ee752d91ba58 - f232789430a080384188d5da89b19d874cf17513 - f674270b1068e4ad51c80dcd528ae996a4fe99ef - 7b9f1e13c750fed76886513071a2b63949181ea4 - fd8595874aa06c8057740001ec465ba76b4af142 - 9a3ba9ca00e73adc3fb17ce8afa532076768023b - 95cc3f4be93d3cb5bb28bb3787f0aace4edb3124 - bc9235cfb80bd64a3bfa959e8d26d5ad1be0bdf4 - def3beb6410857314fe4d17581c4c95ae0c230d1 - 7cc8729dec26c1fd5b06323237acc9ba2bdaaa17 - 6ca87e798bfc448f771d4c264bda22fe2bd82cfc - 78b35f0f7982061576885f944e2ccfaba9573897
resolution: => fixed status: assigned => closed
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=848547
rhbz: [https://bugzilla.redhat.com/show_bug.cgi?id=805917 805917] => [https://bugzilla.redhat.com/show_bug.cgi?id=805917 805917], [https://bugzilla.redhat.com/show_bug.cgi?id=848547 848547]
Metadata Update from @dpal: - Issue assigned to jhrozek - Issue set to the milestone: SSSD 1.9.0 beta 2
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/2016
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.