Learn more about these different git repos.
Other Git URLs
I noticed that capaths generator in SSSD does not handle the case when IPA has directly shared keys with a realm, e.g. for forest roots. SSSD generates capath as FOO.BAR = { EXAMPLE.COM = FOO.BAR } in this case while it should be FOO.BAR = { EXAMPLE.COM = . }. Notice the dot.
FOO.BAR = { EXAMPLE.COM = FOO.BAR }
FOO.BAR = { EXAMPLE.COM = . }
The difference is that client has to perform one more transition via FOO.BAR KDC. In a trace this looks like the following:
[4577] 1519979380.924180: Received TGT for RAWHIDE.VDA.LI; advancing current realm
instead of
[4610] 1519980114.944440: Received TGT for service realm: krbtgt/RAWHIDE.VDA.LI@L.IPA.COOL
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD 2.0
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD 2.1 (was: SSSD 2.0)
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD 2.2 (was: SSSD 2.1)
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD 2.3 (was: SSSD 2.2)
Metadata Update from @thalman: - Issue tagged with: Canditate to close
Metadata Update from @thalman: - Issue untagged with: Canditate to close - Issue tagged with: Patch is welcome
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/4675
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.