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).

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.

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

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.

• master:
  4a9100a
  0d6d493
  c1208b4

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/4429

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.