#1572 [RFE] Integrate local provider with user managment utilities on the system
Closed: wontfix 4 years ago by pbrezina. Opened 11 years ago by dpal.

This would be a pretty bold switch but here is the idea.

There are couple approaches.

  1. Make local provider integrated with files and effectively sync the files in. In this case the utilities that manage users will continue to manage users and groups via files and SSSD would watch for changes and sync them in. The benefits of this approach is that the utilizes do not need to be changed in any way. This would make the adoption easier however we would have to sacrifice the nested groups in the local for example at least for now. Then the SSSD local domain utilities would be focused on managing extra data that does not fit into the passwd file. If SSSD by that time provides D-BUS interface the logic would be: Desktop -> D-BUS Account Service -> SSSD -> Files
  2. Another alternative is to change libuser that is behind the user management utilities on the system to interact with SSSD local domain directly. The library can query is SSSD installed and configured. If it is it will get some configuration information from SSSD and would create users and groups in SSSD DB or local files depending on this configuration data. If SSSD is not there or not configured or configured not to have integration with libuser the utilities would continue working without any change. This would be a pretty bold cross distro effort comparable to the introduction of systemd.

Fields changed

rhbz: => todo

Fields changed

milestone: SSSD 1.11 beta => SSSD 1.12 beta

We decided to go with 1. during the face-to-face meetings on devconf.cz but not in 1.14.

changelog: =>
design: =>
design_review: => 0
fedora_test_page: =>
mark: => 0
milestone: SSSD 1.14 beta => SSSD 1.15 beta
review: => 0
selected: =>
sensitive: => 0

Metadata Update from @dpal:
- 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 reset (from 0)
- 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/2614

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