SSSD / sssd

#848 sysdb API does not need to specify both sysdb context and domain
Closed: Fixed Opened by jhrozek.

Closed: Fixed
Reopen Issue

Many sysdb functions require both a struct sysdb_ctx* and a struct sss_domain_info*. The latter is redundant because the domain is stored in the sysdb context. Passing the domain separately is an artifact from where we had a monolithic cache file for all the domains.

Related to #629

Fields changed

component: SSSD => SysDB
milestone: NEEDS_TRIAGE => SSSD 1.7.0
owner: somebody => jzeleny

Fields changed

status: new => assigned

Fields changed

milestone: SSSD 1.8.0 => SSSD 1.7.0

Fixed in master:

82c3185b2ccc1e99ff6c6d63d09754cbd0705e6c

8a1738f9379a1b8fb5c95c3df649e014ff5a1434

resolution: => fixed
rhbz: =>
status: assigned => closed

Fields changed

rhbz: => 0

Metadata Update from @jhrozek:
- Issue assigned to jzeleny
- Issue set to the milestone: SSSD 1.7.0

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

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.
Metadata
None
None
None
High
defect
SysDB
1.5.4
None
0
0
0
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.