#2205 Always store home directory expansions to sysdb
Closed: wontfix 4 years ago by pbrezina. Opened 10 years ago by jhrozek.

Currently some home directory expansions are stored to sysdb and some are evaluated at runtime by the NSS responder. But at the same time, the ccname expansions can contain %h which should expand into the home directory. Therefore, the home directory should be saved to cache when saving the user so that it's available to the Kerberos provider.


Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.12 beta
rhbz: => todo

Fields changed

owner: somebody => preichl

Fields changed

patch: 0 => 1

I will change next line in description of ticket.[[BR]]
But at the same time, the ccname expansions can contain %h which should expand into the hostname.

s/hostname/home directory/

Fields changed

description: Currently some home directory expansions are stored to sysdb and some are evaluated at runtime by the NSS responder. But at the same time, the ccname expansions can contain %h which should expand into the hostname. Therefore, the home directory should be saved to cache when saving the user so that it's available to the Kerberos provider. => Currently some home directory expansions are stored to sysdb and some are evaluated at runtime by the NSS responder. But at the same time, the ccname expansions can contain %h which should expand into the home directory. Therefore, the home directory should be saved to cache when saving the user so that it's available to the Kerberos provider.

Fields changed

milestone: SSSD 1.12 beta => SSSD 1.12.0

Pavel is on vacation, we will not block the 1.12.0 release and we'll merge the patches when Pavel is back.

milestone: SSSD 1.12.0 => SSSD 1.12.1

Fields changed

rhbz: todo => 0

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 commit these patches when we fork 1.13, because there is a risk of regression with the refactoring.

mark: => 0
milestone: SSSD 1.12.3 => SSSD 1.13 beta

Pavel, does this ticket make sense in the context of InfoPipe?

I think it would be better to make all communication via cache and cache_req instead of expanding the templates in memory in the responder.

cc: => pbrezina
milestone: SSSD 1.13 beta => SSSD 1.13 backlog
sensitive: => 0

This is important to make IFP a first-class citizen.

milestone: SSSD 1.13 backlog => SSSD 1.14 beta

The IFP-as-a-first-class-citizen work will happen in 1.15 as part of the files provider work.

milestone: SSSD 1.14 beta => SSSD 1.15 beta

Metadata Update from @jhrozek:
- Issue assigned to preichl
- 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 adjusted to on (was: 1)
- 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/3247

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