#407 Create public SBUS interface for the sysdb
Closed: Invalid None Opened 14 years ago by sgallagh.

This is a subtask of ticket #44 (Create a -devel package).

In order to support third-party backends, we need to have a stable interface to the sysdb for the backends to be able to update the cache.

We cannot use the existing interface, as it relies on tevent and would mandate its use as a mainloop (which is not an acceptable requirement on most developers)

We will create a new private pipe for this communication.


Deferring to 1.2. It's too soon to release a stable public API.

milestone: SSSD 1.1 => SSSD 1.2

Fields changed

milestone: SSSD 1.2 => SSSD 1.3

Fields changed

priority: blocker => minor

Fields changed

milestone: SSSD 1.5.0 => SSSD 1.6.0

Fields changed

coverity: =>
milestone: SSSD 1.6.0 => SSSD 1.7.0
upgrade: => 0

Fields changed

milestone: SSSD 1.8.0 => SSSD 1.9.0
patch: => 0

Fields changed

blockedby: =>
blocking: =>
milestone: SSSD 1.9.0 => SSSD Deferred
rhbz: =>

Fields changed

rhbz: => 0

The sysdb interface is a private one and should stay this way. I propose we close this ticket. The infopipe is our public interface.

changelog: =>
design: =>
design_review: => 0
feature_milestone: =>
fedora_test_page: =>
mark: => 0
review: => 1
selected: =>
sensitive: => 0

Fields changed

resolution: => wontfix
status: new => closed

Metadata Update from @sgallagh:
- Issue assigned to sgallagh
- Issue set to the milestone: SSSD Patches welcome

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

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