SSSD / sssd

#3368 IFP: Return an error, not a default value for some attributes should not be read
Closed: Fixed by pbrezina. Opened by jhrozek.

Closed: Fixed
Reopen Issue

The IFP interface was designed from the start to return /a value/ always, to make life easier for clients. Normally we return a default value for the type - "" for string, 0 for numbers etc.

But for some values, crashing the client application might actually be easier. One notable example is requesting an UID or GID in a non-POSIX domain. Returning 0 really makes little sense here, we should rather throw an error and let the client deal with it.

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD Future releases (no date set yet)

Fixed in 2.0 as part of sbus reimplementation.

Metadata Update from @pbrezina:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

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

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