#3402 Support alternative sources for the files provider
Closed: Fixed a year ago Opened 2 years ago by jhrozek.

it would be nice to support also nss_altfiles in addition to nss_files with the files provider. To do so, we should extend the list the files provider watches, via some configure-time option the distribution would set.

Not sure if a runtime option would make sense as well, but it would be trivial to implement.


I think it should be only a runtime option (also allowing the selection of file paths to be chosen). This will be most flexible, since it would allow for solutions we haven't considered yet, such as pluggable altfiles.

(Support for a drop directory might be handy as a "better" way to handle per-package username creation as well).

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 1.15.4

2 years ago

Metadata Update from @jhrozek:
- Issue tagged with: easyfix

2 years ago

Implementation notes: Judging by a quick look at the files provider code, it should be enough to:
a) introduce the new option that would default to /etc/passwd for the user part and /etc/group for the group part. The manpage must be amended as well.
b) amend sf_init() to accept a list of files to watch instead of a single user and a single group file. The files names are also stored in the files id context
c) inside sf_init(), loop over the list and call sf_setup_watch() for each of the files
d) sf_passwd_cb() and sf_group_cb() check if the file is the expected one. I think this check can be even dropped (I can't remember the reason why I put it there in the first place) or amended to check against the list of known passwd and group files.

Metadata Update from @jstephen:
- Issue assigned to jstephen

2 years ago

Metadata Update from @jhrozek:
- Issue priority set to: minor

2 years ago

Metadata Update from @jhrozek:
- Issue tagged with: cleanup-one-sixteen

2 years ago

Metadata Update from @jhrozek:
- Issue untagged with: cleanup-one-sixteen
- Issue set to the milestone: SSSD 1.16.0 (was: SSSD 1.15.4)

2 years ago

Since we are required to release a new upstream tarball no later than Friday Oct-20, I'm moving tickets that will not be closed by that date to the next milestone, 1.16.1

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 1.16.1 (was: SSSD 1.16.0)

a year ago

Metadata Update from @jhrozek:
- Issue tagged with: postpone-to-2-0

a year ago

Metadata Update from @jhrozek:
- Issue untagged with: postpone-to-2-0
- Issue set to the milestone: SSSD 2.0 (was: SSSD 1.16.1)

a year ago

If the PR is reviewed soon enough, I'll bump the ticket back to 1.16.x, but I don't want to grow the 1.16.x milestone with tickets that are not strictly needed there.

Metadata Update from @jhrozek:
- Issue tagged with: PR

a year ago

Metadata Update from @jhrozek:
- Issue close_status updated to: Fixed
- Issue set to the milestone: SSSD 1.16.2 (was: SSSD 2.0)
- Issue status updated to: Closed (was: Open)
- Issue tagged with: RFE

a year ago

Login to comment on this ticket.

Metadata