#3569 The cache_req code doesn't check the min_id/max_id boundaries for requests by ID
Closed: Fixed Opened by jhrozek.

Even though a domain sets min_id/max_id limits, the cache_req code currently forwards all requests into the back end. The objects are filtered when saved (see e.g. sysdb_add_user), but at the very least, this is causing unnecessary searches.

I think it would be enough to extend all the .lookup_fn function in each plugin that searches by ID (so, e.g cache_req_group_by_id_lookup() in src/responder/common/cache_req/plugins/cache_req_group_by_id.c, same for user-by-UID and object-by-ID) for a check that returns EOK but a NULL result if the entry is out of the range.


PR:https://github.com/SSSD/sssd/pull/449

Metadata Update from @jhrozek:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1512027

Issue linked to Bugzilla: Bug 1512027

Metadata Update from @jhrozek:
- Issue assigned to amitkumar25nov
- Issue priority set to: critical
- Issue set to the milestone: SSSD 1.16.1
- Issue tagged with: PR, bug

PR:https://github.com/SSSD/sssd/pull/463

  • master: 2af80640f18966d65cf82106059ce3c060df93bf

Metadata Update from @jhrozek:
- 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/4593

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